[llvm-commits] Documentation for GlobalValue lifetime requirements around an ExecutionEngine
Jeffrey Yasskin
jyasskin at google.com
Wed Apr 22 10:32:27 PDT 2009
This is an attempt to describe how users have to handle deleting
GlobalValues that they've emitted code for. I'm not sure I have the
requirements right, so please double-check them.
I believe that there's no way to free the memory that
getOrEmitGlobalVariable allocates, but I haven't documented that on
the theory that it's a bug.
I also haven't mentioned the requirement that no thread, including the
current one, is inside a function's machine code when you call
recompileAndRelinkFunction(that_function). I'm not sure if it's
obvious.
Jeffrey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mach_code_lifetime_doc.patch
Type: application/octet-stream
Size: 3086 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20090422/7d40ca2c/attachment.obj>
More information about the llvm-commits
mailing list