RE: darwin & libgcj ?

["Boehm, Hans" <hans_boehm at hp dot com>]

As far as I'm concerned, the state of the collector currently isn't all that great on MacOSX.  I think the problems aren't hard to deal with.  But I don't have regular access to the platform, and I keep getting bug reports, but no patches.

Incremental collection should probably be disabled for now.  The more serious issue is that, at least in the official gcc tree and in my tree, DYNAMIC_LOADING is not defined in gcconfig.h for MACOSX.  This means that dynamic library data is presumably not being traced by the collector.  Correspondingly, dyn_load.c doesn't know how to find dynamic library data sections on MacOSX, though it does know about FreeBSD.  I'm not sure whether just turning on the FreeBSD code for MACOSX would work.  It's certainly something I would try if I could.  It seems to me that without fixing this, gcj is unlikely to work correctly unless everything is linked statically.

(I don't think I saw all of this thread, and thus may have missed something.)

Hans

> -----Original Message-----
> From: Andreas Tobler [mailto:toa@pop.agri.ch]
> Sent: Monday, January 06, 2003 5:14 AM
> To: Andrew Haley; Jeff Sturm
> Cc: java@gcc.gnu.org
> Subject: Re: darwin & libgcj ?
> 
> 
> 
> 
> -- Original Message --
> 
> >[redirected to Java]
> >Jeff Sturm writes:
> > > On Sun, 5 Jan 2003, Andrew Haley wrote:
> > > >  > Btw, this multiple read is coming from boehm-gc.
> > > >
> > > > Aha!  Well, that is wrong.  Perhaps the linker is 
> failing to do the
> > > > right thing.  But without a system to debug I don't know what is
> > > > causing the problem.
> > > 
> > > I think the simplest thing to do is disable incremental 
> GC on Darwin;
> >see
> > > patch below.  (AFAICT it didn't work anyway; gctest seemed to hang
> > > forever.)
> > > 
> > > With this small patch I get some success on Darwin:
> > > 
> > >                 === libjava Summary ===
> > > 
> > > # of expected passes            335
> > > # of unexpected failures        22
> > > # of expected failures          2
> > > # of unresolved testcases       91
> > > # of untested testcases         16
> 
> Here are mine:
>                 === libjava Summary ===
> 
> # of expected passes            1292
> # of unexpected failures        110
> # of expected failures          4
> # of unresolved testcases       143
> # of untested testcases         163
> 
> Most of them are from this type:
> 
> ERROR: No `main' given in program utilTest
> 
> Later more.
> 
> Andreas
> 
> 
>