Why can static linking with AOT ld successfully link the object files generated by ORC JIT, but JITlink fails to produce a correct executable file?

[Thrrreeee]

When I input a .bc file generated by a multithreaded program, dump the object file generated by ORC JIT, ORC JIT cannot produce a correct executable file, and using llvm-jitlink also fails. However, when I use clang ld to link, it succeeds.
When debugging with LLDB, it outputs the error signal SIGSEGV: invalid address (fault address: 0x0).
What could be the reasons behind this situation?

[llvmbot]

@llvm/issue-subscribers-jitlink

Author: Thrrreeee (Thrrreeee)

When I input a .bc file generated by a multithreaded program, `dump` the object file generated by ORC JIT, ORC JIT cannot produce a correct executable file, and using llvm-jitlink also fails. However, when I use clang `ld` to link, it succeeds. When debugging with LLDB, it outputs the error ` signal SIGSEGV: invalid address (fault address: 0x0).` What could be the reasons behind this situation?

[lhames]

Hi @Thrrreeee.

ORC JIT cannot produce a correct executable file, and using llvm-jitlink also fails.

ORC does not produce executable files (unless you've abused it to create a static linker).

When debugging with LLDB, it outputs the error signal SIGSEGV: invalid address (fault address: 0x0).
What could be the reasons behind this situation?

Is this the JIT'd code, or the executable produced with clang/ld?

If you're generating LLVM IR in a multithreaded context I suspect corruption of your IR, but this bug does not contain sufficient information to say.

Please include detailed error messages (e.g. from llvm-jitlink) and the object file that is failing to link.