Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Tony Kimball <alk AT pobox DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15132.28675.544618.75419@spanky.love.edu>
Date: Tue, 5 Jun 2001 00:37:07 -0500
X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.<li^!8ecK]}3L-
	6`ZQW3}kxy*5]B<KA"&iBl58"/$W-0PP`B7c%'XczR)8T0VN47L`rQlu8qBIX4TJ|v'D%:k7GO%v4A
	Os>Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO
	5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed
Reply-To: alk AT pobox DOT com
To: 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
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F037 AT itdomain002 DOT itdomain DOT net DOT au>
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid

Quoth Robert Collins on Tuesday, 5 June:
: Might I suggest using pthreads? They are the official threads for
: cygwin.

I tried that, but the Boehm GC code depends on implementation details
of Linux threads, and did not trivially port to cygwin.  I'm planning
to compile -mno-cygwin anyhow, so pthreads are not really an option
unless i am willing to add a dependency on the stand-alone pthreads
lib from win32, which I'd rather not do, all other things being equal.

In fact, it is the exponential variety of configuration options which
make getting a good windows java compiler such a bear to wrestle with.
I have made farays into mingw/win32 hosted on linux (i don't recall
the specific problems encountered, off the 'top of my head'),
cygwin/pthreads hosted on cygwin (which was hopelessly slow),
cygwin/pthreads on linux (run-time problems in GC due to
implementation-dependencies in the GC code), and now cygwin/win32
hosted on linux (seemingly now encountering obscure .comm bugs).  It's
hard to know which path to take, and difficult to justify continuing
down any one path to overcome an obstacle, when one knows that there
are other, untried paths, which might avoid all obstacles and provide
a cheap win.


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple