Displaying 2 results from an estimated 2 matches for "_lib_rc_2d_variant".
2012 Dec 01
0
[LLVMdev] MC and admisible function names
...where is rejecting the name
> for one reason or another (intentionally or otherwise).
Yep, apparently those names with characters outside the acceptable range
of the object file format in use (ELF, in my case) are mangled, so this
name:
Fn_.._lib_rc-variant.lp0_17_0x706970
becomes this:
Fn_.._lib_rc_2D_variant.lp0_17_0x706970
> When you call getPointerToFunction in MCJIT, it will ultimately call
> RuntimeDyldImpl::getSymbolLoadAddress to look the name up in a table
> of known function names. That table gets built from the emitted object
> image during the RuntimeDyldImpl::loadObject call. If...
2012 Nov 30
2
[LLVMdev] MC and admisible function names
While using MCJIT, when I define a function with name
Fn_.._lib_rc-variant.lp0_17_0x706970
ExecutionEngine::getPointerToFunction fails to locate it (returns 0).
There is no problem if the function is named Fn_0x706970.
There is no problem with those names using the traditional JIT.
Is there any special limitation on function names for MC/MCJIT?