search for: zlszhh

...; Well, if I recall correctly there's actually a problem with AA being *too* > aggressive for this reason: https://gcc.godbolt.org/z/CXN8Gw > There's a bug report about this somewhere, don't remember where though. That seems to be related purely to TBAA: https://gcc.godbolt.org/z/ZLSzHH What I described should fire if you see the allocation. Alternatively, we can add a new "max object size" attribute [0] which gives a size upper bound for the pointed to memory. In either case, if you know the object pointed to by A is maximal N bytes of size, and the object pointed to b...

...; Well, if I recall correctly there's actually a problem with AA being *too* > aggressive for this reason: https://gcc.godbolt.org/z/CXN8Gw > There's a bug report about this somewhere, don't remember where though. That seems to be related purely to TBAA: https://gcc.godbolt.org/z/ZLSzHH What I described should fire if you see the allocation. Alternatively, we can add a new "max object size" attribute [0] which gives a size upper bound for the pointed to memory. In either case, if you know the object pointed to by A is maximal N bytes of size, and the object pointed to b...

Hi Karl, Roman, On 01/28, Roman Lebedev via llvm-dev wrote: > On Tue, Jan 28, 2020 at 8:09 PM Karl Rehm via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > I was looking into how the global optimization pass fares against > > things like what's reported in > > https://bugs.llvm.org/show_bug.cgi?id=44676 I need to take a closer look but I would have expected