search for: d12090

...edundent expr even if there is an available expr which can be reused. The redundent exprs can be a lot different from existing exprs so that existing cleanup passes cannot remove them. https://llvm.org/bugs/show_bug.cgi?id=24920 https://llvm.org/bugs/show_bug.cgi?id=24442 https://reviews.llvm.org/D12090 and https://reviews.llvm.org/D21313 already relieved the problem somewhat, but it is far from being solved fundamentally. Recently we found another problematic case described in https://llvm.org/bugs/show_bug.cgi?id=29065. And I believe I can create more tests revealing similar problems. In PR2906...

...reused. The redundent exprs can be a lot >> different from existing exprs so that existing cleanup passes cannot >> remove them. >> >> https://llvm.org/bugs/show_bug.cgi?id=24920 >> https://llvm.org/bugs/show_bug.cgi?id=24442 >> >> https://reviews.llvm.org/D12090 and https://reviews.llvm.org/D21313 >> already relieved the problem somewhat, but it is far from being solved >> fundamentally. Recently we found another problematic case described in >> https://llvm.org/bugs/show_bug.cgi?id=29065. And I believe I can >> create more tests re...

Hi Steve it seems the general consensus is that the patch feels like a work-around for a problem with LSR (and possibly other loop transformations) that introduces redundant instructions. It is probably best to file a bug and a few of your test cases. Thanks Gerolf > On Sep 10, 2015, at 4:37 PM, Steve King via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Thu, Sep 10, 2015

> On Aug 23, 2016, at 11:30 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > > Hi Wei, > > I've not seen GCC's SCEV so I cannot make a comparative comment here > (maybe Chris, Andy or Dan can chime in here), but I personally am in > the "make the cleanup passes smarter" camp. We can also try to make > SCEV expansion smarter -- not by

...ng exprs so that existing cleanup passes >> >> cannot >> >> remove them. >> >> >> >> https://llvm.org/bugs/show_bug.cgi?id=24920 >> >> https://llvm.org/bugs/show_bug.cgi?id=24442 >> >> >> >> https://reviews.llvm.org/D12090 and >> >> https://reviews.llvm.org/D21313 >> >> already relieved the problem somewhat, but it is far from being >> >> solved >> >> fundamentally. Recently we found another problematic case >> >> described in >> >> https://llvm....