This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [BC ABI] For entertainment purposes only: gcj-JIT

David Daney wrote:

It has been a little while since I read the details about the BC ABI so
I could be a bit off base, but I was thinking that:

Could you have all uninitialized atable entries point to invalid memory
(perhaps NULL) so that they could be fixed up by the SIGSEGV handler?

The disadvantage of this technique is that signals might have more
overhead than a function call.


Another disadvantage is that SEGVs would become a normal part of program execution, so to debug you'd have to disable stopping on segv in GDB. That would make it hard to see where the real SEGVs are ;-)

Regards

Bryce

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]