[LLVMdev] TLS with MCJIT (an experimental patch)

Kaylor, Andrew andrew.kaylor at intel.com
Wed May 8 13:54:31 PDT 2013

Hi David,

Following up on the problems we discussed yesterday on IRC regarding TLS with MCJIT, I've put together the attached experimental patch.

This patch makes three changes:

1.       SectionMemoryManager is changed to request memory below the 2GB boundary by default.

2.       sys::Memory::allocateMappedMemory is changed to set the MAP_32BIT flag if the requested "near" block is below the 2GB boundary.

3.       RuntimeDyldELF is changed to recognize the possibility of external data symbols.

Of these changes, items 2 and 3 are probably reasonable things to commit into trunk, and depending on how this turns out I will do so.  Item 1 is a bit heavy-handed as presented here, but it suggests the type of thing that subclasses of SectionMemoryManager could do to make this work.  If we had a way to communicate the code model to the memory manager from RuntimeDyld/MCJIT (and we obviously should!) then SectionMemoryManager could do something like this when small or medium memory models are selected on applicable platforms.

When I tried this patch with the test case you provided yesterday it got through the compilation phase with lli using the small code model and the static relocation model, but it ultimately failed (but failed gracefully) because it couldn't resolve the '_ThreadRuneLocale' symbol.  Resolution of external symbols is meant to be handled by the memory manager, so I thought perhaps you could get something working with this patch.

Please give this a try and let me know how it works.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130508/17655ea1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tls-experimental.patch
Type: application/octet-stream
Size: 2471 bytes
Desc: tls-experimental.patch
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130508/17655ea1/attachment.obj>

More information about the llvm-dev mailing list