On Wed, Nov 18, 2009 at 9:33 AM, Duncan Sands <baldrick at free.fr> wrote:> Hi Garrison, > >> - fc merely executes an unwind. > > the code generators do not know how to codegen unwind. Only the > interpreter has support for it. Yes, this sucks. You will need > to call the libgcc unwind routine directly.Really? I thought the JIT supported exceptions via -enable-eh. Reid
Reid Kleckner wrote:> On Wed, Nov 18, 2009 at 9:33 AM, Duncan Sands <baldrick at free.fr> wrote: >> Hi Garrison, >> >>> - fc merely executes an unwind. >> the code generators do not know how to codegen unwind. Only the >> interpreter has support for it. Yes, this sucks. You will need >> to call the libgcc unwind routine directly. > > Really? I thought the JIT supported exceptions via -enable-eh.You mean by lowering to setjmp/longjmp? Maybe, I don't know. It should be easy to find out by trying it. Ciao, Duncan.
> You mean by lowering to setjmp/longjmp? Maybe, I don't know. > It should be easy to find out by trying it.No, with DWARF. There's all this code in the JIT (JITDwarfEmitter.cpp) to register the DWARF with libgcc. Reid
Maybe Matching Threads
- [LLVMdev] Unwinding through a native layer
- [LLVMdev] Unwinding through a native layer
- [LLVMdev] Unwinding through a native layer
- [LLVMdev] Unwinding through a native layer
- [LLVMdev] MCJIT longjmp failure on Win64 - was Invalid or unaligned stack exception on Windows