Displaying 3 results from an estimated 3 matches for "r48715".
2016 Jul 21
2
Remove zext-unfolding from InstCombine
Hi all,
I have a question regarding a transformation that is carried out in InstCombine, which has been introduced by r48715. It unfolds expressions of the form `zext(or(icmp, (icmp)))` to `or(zext(icmp), zext(icmp)))` to expose pairs of `zext(icmp)`. In a subsequent iteration these `zext(icmp)` pairs could then (possibly) be optimized by another optimization (which has already been there before r48715), to replace them...
2016 Jul 27
2
Remove zext-unfolding from InstCombine
...bypassing an earlier fold are wrong IMO.
>
>
> On Thu, Jul 21, 2016 at 6:07 AM, Matthias Reisinger via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> Hi all,
>
> I have a question regarding a transformation that is carried out in InstCombine, which has been introduced by r48715. It unfolds expressions of the form `zext(or(icmp, (icmp)))` to `or(zext(icmp), zext(icmp)))` to expose pairs of `zext(icmp)`. In a subsequent iteration these `zext(icmp)` pairs could then (possibly) be optimized by another optimization (which has already been there before r48715), to replace them...
2016 Aug 04
2
Remove zext-unfolding from InstCombine
...are wrong IMO.
> >
> >
> > On Thu, Jul 21, 2016 at 6:07 AM, Matthias Reisinger via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> > Hi all,
> >
> > I have a question regarding a transformation that is carried out in InstCombine, which has been introduced by r48715. It unfolds expressions of the form `zext(or(icmp, (icmp)))` to `or(zext(icmp), zext(icmp)))` to expose pairs of `zext(icmp)`. In a subsequent iteration these `zext(icmp)` pairs could then (possibly) be optimized by another optimization (which has already been there before r48715), to replace them...