This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: building libgcj on irix 6.5
- To: jsturm at sigma6 dot com
- Subject: Re: building libgcj on irix 6.5
- From: Andrew Haley <aph at pasanda dot cygnus dot co dot uk>
- Date: 9 Dec 1999 15:59:08 -0000
- CC: jmc at cmpharm dot ucsf dot edu, java-discuss at sourceware dot cygnus dot com
> Date: Thu, 09 Dec 1999 11:15:10 -0500
> From: Jeff Sturm <jsturm@sigma6.com>
>
> Andrew Haley wrote:
> > > You might get a successful build with --disable-sjlj-exceptions.
> >
> > It looks as though you've got my libgcj changes in but not my gcj
> > changes. Here's the patch.
>
> Thanks Andrew. I had previously searched for "Sjlj" in gcc/java and
> came up empty.
>
> Out of curiousity... why are setjmp/longjmp exceptions important, and
> why does libgcj only use them on non-Intel, non-SPARC machines by
> default? I don't remember seeing it recently on java-discuss. I'm
> concerned about the extra overhead incurred with setjmp/longjmp on
> platforms where a range-table implementation is available.
That's your choice, and it depends on your application.
Range based exception handling is preferred on many targets because
there's no inline cost when exceptions aren't thrown. On some
machines other choices are preferable, and we simply don't have range
based exception handling for other targets.
So, whatever floats your boat: with gcj we give you the choice.
Andrew.