search for: _myfunc

Displaying 5 results from an estimated 5 matches for "_myfunc".

Did you mean: myfunc
2016 May 19
2
External function resolution: MCJIT vs ORC JIT
...rom the main binary, allowing getSymbolAddressInProcess to find sqr. On MacOS this isn't necessary. > > (3) On MacOS, C names are mangled by prepending an '_'. To maintain consistency with statically linked programs, the JIT uses these mangled names so you need to search for '_myfunc', rather than 'myfunc'. I usually add a 'mangle' function that uses the DataLayout, then search for 'mangle(<name>)', which does the right thing on all platforms. > > I've attached a new version of your code with these changes included. Hope this helps!...
2016 May 20
0
External function resolution: MCJIT vs ORC JIT
...inary, allowing getSymbolAddressInProcess > to find sqr. On MacOS this isn't necessary. > > (3) On MacOS, C names are mangled by prepending an '_'. To maintain > consistency with statically linked programs, the JIT uses these mangled > names so you need to search for '_myfunc', rather than 'myfunc'. I usually > add a 'mangle' function that uses the DataLayout, then search for > 'mangle(<name>)', which does the right thing on all platforms. > > I've attached a new version of your code with these changes included. Hope &gt...
2016 May 22
1
External function resolution: MCJIT vs ORC JIT
...main binary, allowing getSymbolAddressInProcess to find sqr. On MacOS this isn't necessary. >> >> (3) On MacOS, C names are mangled by prepending an '_'. To maintain consistency with statically linked programs, the JIT uses these mangled names so you need to search for '_myfunc', rather than 'myfunc'. I usually add a 'mangle' function that uses the DataLayout, then search for 'mangle(<name>)', which does the right thing on all platforms. >> >> I've attached a new version of your code with these changes included. Hope this...
2013 Mar 29
2
[LLVMdev] x86_stdcallcc @<n> mangling vs. '\1' prefix [was: x86_stdcallcc and extra name mangling on Windows]
Anton, what do you think of David's patch with this test case? OK to commit that? On Wed, Feb 20, 2013 at 12:43 PM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > The patch looks incorrect. The code just needs to handle \1 properly > and clang extended to add explicit \1 to the names which does not > require mangling. > > I do not think that moving whole
2016 May 17
3
External function resolution: MCJIT vs ORC JIT
When using ORC JIT, I'm having trouble with external function resolution (that is, of a function defined in the app, with C linkage). I add a declaration for the function to my IR, and when I use MCJIT, it finds it and all is well, But when I use ORC JIT (I *think* correctly, at least it closely matches what I see in the tutorial), I get an LLVM error, "Program used external function