search for: _elements_exception_handler

...ze: 32bit Now I know what to look for, thanks! On Mon, Aug 20, 2018, at 18:46, Reid Kleckner wrote: > This is 32-bit x86, right? Sounds like the exception handler did not > appear in the /safeseh table.> > If you emit a standalone .s file, do you see something like > `.safeseh _elements_exception_handler` somewhere in there? If > not, that's a problem. I think it would also be a problem if > _elements_exception_handler is imported. If so, try making a > thunk for it.> > You can also try running `dumpbin /loadconfig` (or equivalently llvm- > readobj -coff-load-config) on your...

...n ConsoleApplication830.exe: 0xC00001A5: An invalid exception handler routine has been detected (parameters: 0x00000001). With some fairly simple SEH enabled routine: define i32 @__elements_entry_point_main(%._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s*) #0 personality i8* bitcast (i32 ()* @_elements_exception_handler to i8*) !dbg !61 { BasicBlock0: %1 = alloca %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* store %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* %0, %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s** %1 call void @llvm.dbg.declare(metadata %._gt2a_RemObjects_d_Elements_d_System_...

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. Rui Ueyama <ruiu at google.com>...

...trunk on Mar, 15). The crash happens when SelectionDAGBuilder::lowerInvokable tries to access EH info of this function: ms_t26_RemObjects_d_Elements_d_EUnit_d_Runnerb_RunChildrennt2a_RemObjects_d_Elements_d_EUnit_d_RunContext This happens because LLVM doesn't know your personality function (@_elements_exception_handler), so I suggest looking at llvm::classifyEHPersonality function as well. ________________________________________ От: llvm-dev <llvm-dev-bounces at lists.llvm.org> от имени Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> Отправлено: 14 марта 2018 г. 15:42 Кому: llvm-dev Тема: [llvm-...

I have a fairly recent LLD/LTO llvm crashing on DIE *ContextDIE = getOrCreateContextDIE(Context) being null for a (local) variable. (Context is a DICompileUnit in this case, but it's not present in MDNodeToDieMap so it returns null. callstack is: llc.exe!llvm::DwarfUnit::getOrCreateTypeDIE(const llvm::MDNode * TyNode) Line 718 C++ llvm::DwarfUnit::addType(llvm::DIE & Entity, const

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...

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

...rash happens > when SelectionDAGBuilder::lowerInvokable tries to access EH info of this function: > > ms_t26_RemObjects_d_Elements_d_EUnit_d_Runnerb_RunChildrennt2a_RemObjects_d_Elements_d_EUnit_d_RunContext > > This happens because LLVM doesn't know your personality function (@_elements_exception_handler), so I suggest looking > at llvm::classifyEHPersonality function as well. > hi, I've updated my testcase https://www.dropbox.com/s/ugv9sfqouhlszff/repro.tar?dl=0 to use the standard exception handler. Now it fails with llvm-6.0 from the website exactly the same as it does with my cus...

...y 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...

...crash happens > when SelectionDAGBuilder::lowerInvokable tries to access EH info of this function: > > ms_t26_RemObjects_d_Elements_d_EUnit_d_Runnerb_RunChildrennt2a_RemObjects_d_Elements_d_EUnit_d_RunContext > > This happens because LLVM doesn't know your personality function (@_elements_exception_handler), so I suggest looking > at llvm::classifyEHPersonality function as well. > hi, I've updated my testcase https://www.dropbox.com/s/ugv9sfqouhlszff/repro.tar?dl=0 to use the standard exception handler. Now it fails with llvm-6.0 from the website exactly the same as it does with my custo...