Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <063301c19902$7877b560$0200a8c0@lifelesswks> From: "Robert Collins" To: "Stephen Perry" , "Laurence F. Wood" , "Cygwin AT Cygwin. Com" References: Subject: Re: Cygwin for windows to linux migration Date: Wed, 9 Jan 2002 22:40:41 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 09 Jan 2002 11:40:41.0559 (UTC) FILETIME=[776B4E70:01C19902] ----- Original Message ----- From: "Stephen Perry" > Other than templates, if you change all win32 calls to POSIX calls you > should be good to go. Including thread calls. Does cygwin support pthreads > on windows? That would be very cool, for porting purposes. Yes, nearly complete implementation (only one key feature - cancellation points - missing)... Oh signals per thread needs a little work. Apparently the code is pretty fast :}. (Another project, an IBM mainframe emulator bench tested cygwin threads vs Native threads vs libpthread-win32 (another pthreads-on-win32 library, but unable to be as complete as cygwin (can't assume a unix environment)), and native threads where (of course) fastest, but we came out even with libpthread-win32, and that was before some major speed enhancements. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/