| Issue |
87516
|
| Summary |
LLJITWithExecutorProcessControl example crashes on M2 Max
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
jkrueger
|
Just running the LLJITWithExecutorProcessControl example binary after a fresh build on an M2 Max MacBook Pro (on Sonoma) crashes with the following stack trace.
Stack dump:
0. Program arguments: bin/LLJITWithExecutorProcessControl
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0 LLJITWithExecutorProcessControl 0x00000001049a6024 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56
1 LLJITWithExecutorProcessControl 0x00000001049a4eec llvm::sys::RunSignalHandlers() + 112
2 LLJITWithExecutorProcessControl 0x00000001049a66b8 SignalHandler(int) + 360
3 libsystem_platform.dylib 0x000000018f03b584 _sigtramp + 56
4 LLJITWithExecutorProcessControl 0x0000000104635efc main + 3256
5 dyld 0x000000018ec820e0 start + 2360
[1] 84473 illegal hardware instruction bin/LLJITWithExecutorProcessControl
I am writing a Clojure compiler using LLVM myself, and can reproduce this in my own code, when using the Orc JIT in combination with lazy reports, in a similar way to this example.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
