building libgcj on irix 6.5

Thu Dec 9 08:48:00 GMT 1999

 What would also be nice is if you identified those instructions that can cause
null pointer exceptions and then turned asynchronous_exceptions off. Should 
result in a nice reduction in the size of the exception related meta information
for the range based scheme. At least when compiling from bytecode, this is
actually not too hard to do; it's only a handful of bytecode instructions. I assume 
it's also not hard when compiling from source.
	- Godmar
>>> Andrew wrote:
> > On some machines other choices are preferable, and we simply don't
> > have range based exception handling for other targets.
>> If someone can implement a configure check for range based EH, then we
> can set a reasonable default at configure time (my understanding is
> that the pc range based scheme is preferable in general).
>> Also, given configure.host patches, we can hard code different
> defaults for different targets.
>> AG
>> -- 
> Anthony Green Cygnus Solutions
> Sunnyvale, California
>