search for: classifyehperson

...he crash, personality functions were still on the LandingPadInst itself. I agree that typically its fine to be able to use opaque values. Unless we actually have to introspect the personality Function*, eg, for calling conventions, then I think its fine to allow any value. In fact, it looks like classifyEHPersonality was written to support this. Pete >> >> (especially with pointer bitcasts (which will go away, eventually) - if I have a global variable I've put some executable bytes in and I cast a pointer to that global variable to a pointer to a function, I would expect that should be in...

...er::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-dev] lld/lto/win32 crash on DIE code I have a fa...

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

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

...s 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 custom build.

Hi Scott, Sorry for the late reply, I was out of office during the holidays. 1. A def node can reach either a use node, or another def node. In the highlighted phi node (p3224), the def (d3225) reaches another def (1598) in statement (s1597), that’s why it’s needed. 2. The reason why the def of R11 in s1578 is not connected directly to the use in s1725 is that there may be an intervening