search for: addfragmentoffset

Hi, I'm hitting an assertion "overlapping or duplicate fragments" in the DWARF codegen in addFragmentOffset(). This originates from a duplicated dbg.declare intrinsic, declaring the same fragment twice. The duplicated call was generated by the jump threading pass. I have a patch (see below) that removes simply such duplicates, but I'm not sure whether that is the right approach. Cheers, Björn dif...

...eDbgDeclare()/FindAllocaDbgDeclare() all seems to think there is only one dbg.declare connected to one alloca. At least they all ignore all except the first one found. Later loop unroll comes and unrolls the loop and then suddenly we have two absolutely identical dbg.declares and the assert in addFragmentOffset() blows. Who's at fault? There is also an existing testcase that checks that there _are_ indeed two dbg.declares to a single alloca: Transforms/Inline/alloca-dbgdeclare-merge.ll Regards, Mikael On 09/19/2017 02:27 PM, Björn Steinbrink via llvm-dev wrote: > Hi, > > I'm hitting...

...clare()/FindAllocaDbgDeclare() all seems to think there is only one dbg.declare connected to one alloca. At least they all ignore all except the first one found. > > Later loop unroll comes and unrolls the loop and then suddenly we have two absolutely identical dbg.declares and the assert in addFragmentOffset() blows. Who's at fault? Without having read the code yet, my intuition says that the unroller should not be duplicating dbg.declares, only dbg.values. -- adrian > > There is also an existing testcase that checks that there _are_ indeed two dbg.declares to a single alloca: Transforms/...

On Tue, Sep 19, 2017 at 8:40 AM, Adrian Prantl via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Later loop unroll comes and unrolls the loop and then suddenly we have > two absolutely identical dbg.declares and the assert in addFragmentOffset() > blows. Who's at fault? > > Without having read the code yet, my intuition says that the unroller > should not be duplicating dbg.declares, only dbg.values. > I think it's a bug in both places: the backend should tolerate identical, duplicate dbg.declares, and the loop un...

...wrote: > > On Tue, Sep 19, 2017 at 8:40 AM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Later loop unroll comes and unrolls the loop and then suddenly we have two absolutely identical dbg.declares and the assert in addFragmentOffset() blows. Who's at fault? > > Without having read the code yet, my intuition says that the unroller should not be duplicating dbg.declares, only dbg.values. > > I think it's a bug in both places: the backend should tolerate identical, duplicate dbg.declares, I guess that's...

Hi folks, While building openmpi.4.0.0(Optimized debug build), using trunk clang we encountered a crash(assertion failure). Initially assertion seems trivial: [...] void llvm::DwarfExpression::addFragmentOffset(const llvm::DIExpression*): Assertion `FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"' failed. [...] But, narrowing to RC. We discovered "-O3 -enable-partial-inlining" pass which is doing some DebugInfo manipulation, later triggering this....

...Sep 19, 2017 at 8:40 AM, Adrian Prantl via llvm-dev >> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> > Later loop unroll comes and unrolls the loop and then suddenly we have two absolutely identical dbg.declares and the assert in addFragmentOffset() blows. Who's at fault? >> >> Without having read the code yet, my intuition says that the >> unroller should not be duplicating dbg.declares, only dbg.values. >> >> >> I think it's a bug in both places: the backend should tolerate >> iden...

...mar, Sourabh Singh <SourabhSingh.Tomar at amd.com> wrote: > > Hi folks, > > While building openmpi.4.0.0(Optimized debug build), using trunk clang we encountered a crash(assertion failure). > > Initially assertion seems trivial: > […] > void llvm::DwarfExpression::addFragmentOffset(const llvm::DIExpression*): Assertion `FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"' failed. > […] > > But, narrowing to RC. We discovered “-O3 -enable-partial-inlining” pass which is doing some DebugInfo manipulation, later triggering t...

...r, Sourabh Singh <SourabhSingh.Tomar at amd.com<mailto:SourabhSingh.Tomar at amd.com>> wrote: Hi folks, While building openmpi.4.0.0(Optimized debug build), using trunk clang we encountered a crash(assertion failure). Initially assertion seems trivial: […] void llvm::DwarfExpression::addFragmentOffset(const llvm::DIExpression*): Assertion `FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"' failed. […] But, narrowing to RC. We discovered “-O3 -enable-partial-inlining” pass which is doing some DebugInfo manipulation, later triggering this. Reproducib...