@Robert_Crovella If you are familiar with rust the language, i am writing a rustc backend to generate NVVM IR so that i can write gpu kernels using rust. The issue is that when it gets to the final stage of calling libnvvm, it segfaults. I am giving it 5 modules in total, the program, compiler_builtins (which is basically just i128 emulation functions), core (a gigantic module, about a hundred kloc or so in llvm ir), libdevice, and another custom module which wraps compiler_builtins as well as emulates i8 overflowing intrinsics using i16 llvm intrinsics.
The issue happens only with compiler_builtins and core, the program and others compile just fine. compiler_builtins is about 38kloc of functions that call eachother, so isolating specific parts would be a challenge.
The reason i believe this should be a bug is because it is not caught by the verifier, the compiler just segfaults when compiling. And while it is almost definitely caused by invalid IR, i believe it should catch this more gracefully. I could submit a bug report with the compiler_builtins file, it should be very easy to debug with debug symbols since it is trying to dereference a null pointer according to lldb.