Displaying 4 results from an estimated 4 matches for "01__elements_exception_handler".
2018 Mar 30
1
[LLD] Mixing bitcode and native code
Clang may be avoiding this problem because it will always emit
"\01__elements_exception_handler at 20" as the function name. It probably does
that for precisely this reason.
On Fri, Mar 30, 2018 at 11:55 AM Carlo Kok via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> The problem is a bitcode implementation that has a stdcall function that's
> used from native code. 1 s...
2018 Mar 30
0
[LLD] Mixing bitcode and native code
The problem is a bitcode implementation that has a stdcall function that's used from native code. 1 side has _elements_exception_handler, compiled that would be __elements_exception_handler at 20 due to stdcall. The native bit has the mangled name and the linker can't find it as the bitcode indexes have it without mangling.
I'll try to prepare a testcase when I get back in the office.
2018 Apr 03
0
[LLD] Mixing bitcode and native code
...s my problem was the reverse; the definition did NOT have stdcall properly set; which is why i wasn't found. Setting that and everything worked. Thanks for the help.
On Fri, Mar 30, 2018, at 23:40, Reid Kleckner wrote:
> Clang may be avoiding this problem because it will always emit "\01__elements_exception_handler at 20" as the function name. It probably does that for precisely this reason.
>
> On Fri, Mar 30, 2018 at 11:55 AM Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> The problem is a bitcode implementation that has a stdcall function that's used from native co...
2018 Mar 30
2
[LLD] Mixing bitcode and native code
Mixing native and bitcode files should just work, and that happens all the
time, as most programs need at least crt.o (which is a precompiled native
object file containing startup code).
Could you elaborate the issue a bit? It might be a bug in lld.
On Fri, Mar 30, 2018 at 3:11 AM Carlo Kok via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Fri, Mar 30, 2018, at 11:23, Carlo Kok