search for: getjitresolv

...olver. However, these two classes work very closely together, so I think there should only be a single lock object. Does this seem reasonable? Additionally, it only seems to make sense that there is a single JITResolver instance. Thus, I am going to force code to hold the lock before calling "getJITResolver." Does that seem reasonable? Thanks, Evan Jones

...think it would be more straight-forward to have a single lock that the jit resolver can aquire. Makes sense to me at least :) > Additionally, it only seems to make sense that there is a single > JITResolver instance. Thus, I am going to force code to hold the lock > before calling "getJITResolver." Does that seem reasonable? Yes, there can be only one JITResolver. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

...); > + Please don't add getTargetMachine() to jit. MachineCodeEmitter can keep a reference to MachineFunction or something like that. > } > ~JITEmitter() { > delete MemMgr; > + if (ExceptionHandling) delete DE; > } > > JITResolver &getJITResolver() { return Resolver; } > @@ -359,11 +449,606 @@ > void deallocateMemForFunction(Function *F) { > MemMgr->deallocateMemForFunction(F); > } > + > + virtual void EmitLabel(uint64_t LabelID) { > + if (LabelLocations.size() <= LabelID) > +...

...to jit. MachineCodeEmitter can > keep a reference to MachineFunction or something like that. > > OK >> } >> ~JITEmitter() { >> delete MemMgr; >> + if (ExceptionHandling) delete DE; >> } >> >> JITResolver &getJITResolver() { return Resolver; } >> @@ -359,11 +449,606 @@ >> void deallocateMemForFunction(Function *F) { >> MemMgr->deallocateMemForFunction(F); >> } >> + >> + virtual void EmitLabel(uint64_t LabelID) { >> + if (LabelLocations.size() &...

Hi everyone, Here's a patch that enables exception handling when jitting. I've copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may need to factorize it, but the functionality is there and I'm very happy with it :) lli should now be able to execute the output from llvm-gcc when using exceptions (the UnwindInst instruction is not involved in this patch). Just add the

...> DOUT << "JIT is managing a GOT\n"; > } > + > + if (ExceptionHandling) DE = new JITDwarfEmitter(jit); > } > ~JITEmitter() { > delete MemMgr; > + if (ExceptionHandling) delete DE; > } > > JITResolver &getJITResolver() { return Resolver; } > @@ -384,6 +401,24 @@ > void deallocateMemForFunction(Function *F) { > MemMgr->deallocateMemForFunction(F); > } > + > + virtual void emitLabel(uint64_t LabelID) { > + if (LabelLocations.size() <= LabelID) > + Label...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL: