This is the mail archive of the
mailing list for the GCC project.
Re: Porting gcj to i386-darwin
Sandro Tolaini writes:
> On 10/mar/2006, at 20:42, Tom Tromey wrote:
> > libffi and mudflap were covered by Paolo and Andrew.
> I have done some work on sysv.S and now libffi compiles fine on OSX/
> Intel. Unfortunately, I had to put some #ifdef __APPLE__ this file
> because Apple ships an old cctools with as that doesn't understand
> some directives. My patch works on the 4.0 branch, I tried it on the
> 4.2 branch but libffi has changed in such a way that compiling it
> with the Apple as is not easily feasible (and I don't chew enough
> assembly code to change it).
You need to build everything from the same branch: gcc, libffi,
everything. Don't use some other compiler.
> > For libjava some porting may be required, though it shouldn't be very
> > much.
> libjava compiled out-of-the-box after tweaking the configure scripts.
> For boehm, I copied the one in the 4.2 branch and applied a patch
> that Hans should have already put in the current CVS version.
> > For best results you will want to make sure that the code to turn
> > signals into exceptions works properly. This is both OS- and
> > architecture dependent. I haven't looked at the x86 darwin port,
> > perhaps some gcc hacking is required.
> How can I try this? Is there some test case I can use?
To begin with, don't worry about it. You can have a fully-working
port without handling these traps, because we have default fallback
code for memory accesses and divides.