boehm-gc .comm problem

Tue Jun 5 17:18:00 GMT 2001

----- Original Message -----
From: "Tony Kimball" <alk@pobox.com>
To: <robert.collins@itdomain.com.au>
Cc: <java@gcc.gnu.org>
Sent: Wednesday, June 06, 2001 8:15 AM
Subject: RE: boehm-gc .comm problem
>> Many thanks to Robert and Tom for the helpful advice. The consensus
> being that mingw32 is the better target to work with at the moment,
> I am shifting my focus to that target.

no probs..
>> The rest of this message is to answer Robert's helpful questions.
>> Quoth Robert Collins on Tuesday, 5 June:
> : I'd say that you need to build a mingw cross-compiler, not a cygwin
> : cross compiler for starters.
>> Tom Tromey seemed to agree that Mingw would be a better approach,
> so I'm going to go with this consensus advice and see what happens.

My advice was based on _your_ preferred target of mingw. I suspect
cygwin is an easier target, as a port has been achieved, but not knowing
the requirements of your project, all I could do is help streamline your
path - you already had a goal of mingw, AFAICouldT.
> : The boehm-gc code seemed to work fine for me when I spent a few days
> : getting libgcj going on cygwin.
>>> : You can look in the java archives or the
> : cygwin-apps archives
>> I've been carefulling tracking the java@ list, but cygwin-apps is not
> searchable, unfortunately. I did check the last three months for

Not searchable? there are at least two separate searchable archives!
Try http://www.cygwin.com/ml/cygwin-apps/
> tidbits, though, and saw the mid-April messages. Speaking of which, a
> propos your thread on cygwin-apps, and in case you aren't already
> aware of it, the -fbuiltin/-fno-builtin switch is documented to
> control the availablility of the 'alloca' alias for __builtin_alloca.

Ah, no I wasn't. Thank you.
> : for the results from that. Another net contributor
> : took what I'd done and finished it off - getting to the point of
being
> : able to run the tests. I'm not sure of the results of the test-runs,
or
> : the current status.
>> I think I have all of David Billinghurst's mods in my local tree.
>> : > cygwin/pthreads hosted on cygwin (which was hopelessly slow),
> :
> : Where was it slow? What version of cygwin? (Pre-1.3.0 all
thread-related
> : calls where serialised).
>> I am using the current version installed by setup.exe.
> I suspect most of the time was consumed inside make.exe with shell
> forks or something like that. It would take at least a day to do
> a build from scratch on cygwin, on my P3-700 laptop.

So build time was the issue, not runtime? That makes more sense :]. For
me, on a PIII 500 it took ~ 4 hours to build. Cygwin 1.3.1 had a nasty
20% slowdown due to a bug. I believe that has been fixed.
> : > cygwin/pthreads on linux (run-time problems in GC due to
> : > implementation-dependencies in the GC code),
> :
> : I don't see how that differs from cygwin/pthreads on cygwin, unless
your
> : cross-compiler was broken.
>> The difference is that I actually had the patience to go down this
> path long enough to encounter a bug:-)

Ah. OK, so we're back to the issueing of the .comp instructions, which
is too deep in gcc for me to really be helpful. So I'll bow out of this
at this point, and wish you good luck.
Rob