Dynamically generated code and DWARF exception handling

[Tom Tromey]

>>>>> "jacob" == jacob navia <jacob@jacob.remcomp.fr> writes:

>> Unfortunately things are also worse for libgcj, in that we need to be
>> able to generate stack traces as well, and the trampoline function
>> approach won't work there.
>> 

jacob> ????? Sorry I do not follow here

The java runtime needs to be able to examine the current stack and
find out what methods (and map back to classes and then class loaders)
are executing.  So a little shim like I mentioned won't work, as the
whole stack trace has to be created.

>> Longer term, yeah, gcc's unwinder needs a JIT API, and then the
>> various JITs need to be updated to use it.  At least LLVM appears to
>> be headed this direction.
>> 
jacob> Very interesting but maybe you could be more specific?

jacob> I browsed that "llvm" and seems a huge project, as libgcj is. To go
jacob> through all that code to find how they implement this, will be
jacob> extremely difficult. If you could give me some hints as to where is
jacob> the needle in those haystacks I would be really thankful.

Unfortunately this work hasn't started, at least not that I'm aware.
So, it isn't in there yet, just planned.

Tom