libjava status on Tru64 UNIX V5.1

Mon Mar 25 16:46:00 GMT 2002

> Ideally we'd focus our efforts on making Dwarf-2 exceptions work well
> for us everywhere. Then we can reserve -fcheck-references for
> MMU-less platforms, and we don't need to use sjlj exceptions. I think
> using the latter is problematic because it puts us at odds with the
> desired C++ default; system integrators will most likely always pick
> Dwarf-2 over sjlj.

[Regarding the last point of C++ default/libjava mismatch: How true.]
If I have an ELF/DWARF2 platform which detects the exception model as
`call frame' and has java-signal.h pointing to default-signal.h
instead of dwarf2-signal.h should my highest priority related to
libjava be changing this? Not a trick question. Assuming this was a
major bug in my port's configuration, I started looking at it early
last week.
Why does Linux/i386 (which uses DWARF2, no?) require a special
i386-signal.h instead of using the generic dwarf2-signal.h?
Regards,
Loren