[LLVMdev] The same context; different memory space

Jasmin Jahic jasmin.jahic at gmail.com
Mon Jun 9 12:16:44 PDT 2014


Hello,

I asked this question a few days ago, but it seems that thread died out:

I have a MAIN program which includes LLVM libraries and loads one bc file.
>From MAIN I execute different functions from the bc file using LLVM
interpreter.  On the LLVM website it is said:
"LLVMContext is an opaque class in the LLVM API which clients can use to
operate multiple, isolated instances of LLVM concurrently within the same
address space." - It seems that this is not correct or I'm not
understanding it properly.

One context is used to create two modules, and based on modules all other
things needed for the execution (engine builders, execution engines,
functions). When functions are executed (sequentially), they are obviously
executed in different memory space. I have verified this over access to the
global variable.

However, if functions are executed using the same execution engine
(context, module and execution builder the same), then they are executed in
the same memory space. But using one execution engine is not suitable for
me, because one execution engine means one stack.

One option is to use different stack frames. Before trying that, I just
wanted to ask is there a different way for sharing memory space between
more execution engines?

Best regards,
Jasmin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140609/ea107cfc/attachment.html>


More information about the llvm-dev mailing list