Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <140D21516EC2D3119EE7009027876644049B5E6E@hplex1.hpl.hp.com> From: "Boehm, Hans" To: "'alk AT pobox DOT com'" , robert DOT collins AT itdomain DOT com DOT au Cc: java AT gcc DOT gnu DOT org, cygwin AT cygwin DOT com Subject: RE: boehm-gc .comm problem Date: Tue, 5 Jun 2001 09:02:24 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Tony Kimball [mailto:alk AT pobox DOT com] > cygwin/pthreads on linux (run-time problems in GC due to > implementation-dependencies in the GC code) > I believe those should be pretty minimal at this point, at least if you start with what's now in the trunk. I'm sure the code there is not technically pthreads conforming, but I'm under the impression that it should be possible to get it to work fairly easily on most pthreads platforms. I'd be interested in any problems, since my long term goals is to use the linux_threads.c code to provide suppport for all pthreads platforms (thus eliminating the separate support for Solaris and Irix). The same code already works for both Linux threads and HP/UX pthreads. (There is also Tru64 support, which I can't test.) Hans -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple