search for: getorcreatecontextdi

Displaying 12 results from an estimated 12 matches for "getorcreatecontextdi".

Did you mean: getorcreatecontextdie
2017 Nov 15
2
workaround for debug info bug?
Seems like something infinite-recursion like to me: $ clang --version clang version 6.0.0 (trunk 317833) Target: powerpc64le-unknown-linux-gnu $ clang -c test.ll warning: overriding the module target triple with powerpc64le-unknown-linux-gnu [-Woverride-module] ... #255 0x0000000012b07a78 llvm::DwarfUnit::getOrCreateTypeDIE(llvm::MDNode const*) ... So I'd say it reproduces. On Wed, Nov 15,
2013 Nov 15
1
[LLVMdev] DebugInfo: LTO Metadata Size reduction by removing some cycles
>From a thread with Adrian on llvm-commits I looked a little at cases where DwarfCompileUnit's getOrCreateContextDIE's "fallback to return the CU" didn't fire when a CU DIE was required (ie: when the "getDIE" call actually found the CU before the fallback happened) This seems unnecessary, and any case where we do this (where a metadata node has a non-null context DIE pointing to the...
2018 Mar 21
2
lld/lto/win32 crash on DIE code
Op 21-3-2018 om 10:28 schreef Evgeny Leviant: > It looks the problem lies in how your compiler generates debug info. LLVM doesn't > expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: > > DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { > - if (!Context || isa<DIFile>(Context)) > + if (!Context || isa<DIFile>(Context) || isa<DICompileUnit>(Context)) > > However, I suggest talking to someone with in-depth debug info experience, as the problem > itself seems to be not re...
2018 Mar 14
3
lld/lto/win32 crash on DIE code
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 & Enti...
2018 Mar 21
0
lld/lto/win32 crash on DIE code
...: [llvm-dev] lld/lto/win32 crash on DIE code Op 21-3-2018 om 10:28 schreef Evgeny Leviant: > It looks the problem lies in how your compiler generates debug info. LLVM doesn't > expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: > > DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { > - if (!Context || isa<DIFile>(Context)) > + if (!Context || isa<DIFile>(Context) || isa<DICompileUnit>(Context)) > > However, I suggest talking to someone with in-depth debug info experience, as the problem > itself seems to be not rel...
2018 Mar 21
3
lld/lto/win32 crash on DIE code
...crash on DIE code > > Op 21-3-2018 om 10:28 schreef Evgeny Leviant: >> It looks the problem lies in how your compiler generates debug info. LLVM doesn't >> expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: >> >> DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { >> - if (!Context || isa<DIFile>(Context)) >> + if (!Context || isa<DIFile>(Context) || isa<DICompileUnit>(Context)) >> >> However, I suggest talking to someone with in-depth debug info experience, as the problem >> itself...
2018 Mar 21
0
lld/lto/win32 crash on DIE code
It looks the problem lies in how your compiler generates debug info. LLVM doesn't expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { - if (!Context || isa<DIFile>(Context)) + if (!Context || isa<DIFile>(Context) || isa<DICompileUnit>(Context)) However, I suggest talking to someone with in-depth debug info experience, as the problem itself seems to be not related to LTO. ___________...
2018 Mar 21
0
lld/lto/win32 crash on DIE code
...crash on DIE code > > Op 21-3-2018 om 10:28 schreef Evgeny Leviant: >> It looks the problem lies in how your compiler generates debug info. LLVM doesn't >> expect DIDerivedType scope to be an instance of DICompileUnit. Here is a quick fix: >> >> DIE *DwarfUnit::getOrCreateContextDIE(const DIScope *Context) { >> - if (!Context || isa<DIFile>(Context)) >> + if (!Context || isa<DIFile>(Context) || isa<DICompileUnit>(Context)) >> >> However, I suggest talking to someone with in-depth debug info experience, as the problem >> itself...
2018 Mar 16
0
lld/lto/win32 crash on DIE code
..._________ От: 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 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 &...
2018 Mar 20
2
lld/lto/win32 crash on DIE code
Op 20-3-2018 om 12:40 schreef Evgeny Leviant: > This one triggers an assertion in calculateSEHStateNumbers due to weird catchpad instruction > in @_island_debug_invoke and many other functions. The code expects either pointer to a filter > function or null in first operand, while you're passing pointer to structure: > > catchpad within %80 [{i8*, i8*}* anon..., ...] > >
2013 Oct 15
0
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
All that being said, I'm asking these questions because I don't know for sure - but that we cannot add unjustified complexity, we must understand why it is there and have tests to demonstrate its necessity. So to play some Devil's Advocate - how does your patch handle the following situation: hdr.h: struct foo { template<typename T> struct bar { }; }; src1.cpp: #include
2013 Oct 15
4
[LLVMdev] [Debug Info PATCH] for support of ref_addr and removal of DIE duplication
On Tue, Oct 15, 2013 at 1:56 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Tue, Oct 15, 2013 at 1:37 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> >> On Tue, Oct 15, 2013 at 1:22 PM, Manman Ren <manman.ren at gmail.com> wrote: >> >>> >>> >>> >>> On Tue, Oct 15, 2013 at