search for: a_module

Displaying 3 results from an estimated 3 matches for "a_module".

Did you mean: _module
2009 Mar 27
4
[LLVMdev] Connecting JITted code to gdb
Hi all. I'm working on the recently-announced unladen-swallow project, and I'm having a bit of trouble getting gdb to step into functions I've compiled with LLVM's JIT compiler. The attached a_module.ll is the module I produce from compiling def foo(r): for i in r: pass I'm JIT-compiling and running foo() with: typedef PyObject *(*NativeFunction)(PyFrameObject *); llvm::ExecutionEngine *engine = ...->getExecutionEngine(); NativeFunction native = (NativeFunction)engine->g...
2009 Mar 27
0
[LLVMdev] Connecting JITted code to gdb
...disassemble the code. On Mar 26, 2009, at 11:35 PM, Jeffrey Yasskin wrote: > Hi all. I'm working on the recently-announced unladen-swallow project, > and I'm having a bit of trouble getting gdb to step into functions > I've compiled with LLVM's JIT compiler. The attached a_module.ll is > the module I produce from compiling > > def foo(r): > for i in r: > pass > > I'm JIT-compiling and running foo() with: > > typedef PyObject *(*NativeFunction)(PyFrameObject *); > llvm::ExecutionEngine *engine = ...->getExecutionEngine(); > Nati...
2009 Mar 27
2
[LLVMdev] Connecting JITted code to gdb
...! > On Mar 26, 2009, at 11:35 PM, Jeffrey Yasskin wrote: > >> Hi all. I'm working on the recently-announced unladen-swallow project, >> and I'm having a bit of trouble getting gdb to step into functions >> I've compiled with LLVM's JIT compiler. The attached a_module.ll is >> the module I produce from compiling >> >> def foo(r): >>  for i in r: >>    pass >> >> I'm JIT-compiling and running foo() with: >> >>       typedef PyObject *(*NativeFunction)(PyFrameObject *); >>       llvm::ExecutionEngine...