Displaying 5 results from an estimated 5 matches for "canonicaliztion".
Did you mean:
canonicalization
2016 Mar 22
0
RFC: A change in InstCombine canonical form
...need to uncover and fix between now and the time that typeless pointer is available. That means it is likely that we have multiple such fixes in the code and then we have to remove each one of them. (And means each one of those has to be done properly to be easily remove-able).
>
> Changing canonicaliztion of memcpy, will be removing a couple of lines of code. I am not sure about the size of backend changes to optimize load-store patterns. But I expect it to be small.
Are you saying that the canonicalization you want to change is temporary till we get the typeless pointers?
--
Mehdi
>
>...
2016 Mar 22
2
RFC: A change in InstCombine canonical form
...er and fix between now and the time that typeless pointer
> is available. That means it is likely that we have multiple such fixes in
> the code and then we have to remove each one of them. (And means each one
> of those has to be done properly to be easily remove-able).
>
> Changing canonicaliztion of memcpy, will be removing a couple of lines of
> code. I am not sure about the size of backend changes to optimize
> load-store patterns. But I expect it to be small.
>
>
> Are you saying that the canonicalization you want to change is temporary
> till we get the typeless pointe...
2016 Mar 22
1
RFC: A change in InstCombine canonical form
On Tue, Mar 22, 2016 at 5:44 PM, Ehsan Amiri via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Thanks.
>
> *Phillip, *As Hal said I do not think (1) is a very large item. Please
> let me know if I am mistaken.
>
> *David *I think (1) is more inline with typeless pointer work than (2).
> Contributing to typeless pointer work will be great, but given its unknown
>
2016 Mar 22
0
RFC: A change in InstCombine canonical form
...at we
> > > have
> > > multiple such fixes in the code and then we have to remove each
> > > one
> > > of them. (And means each one of those has to be done properly to
> > > be
> > > easily remove-able).
> >
>
> > > Changing canonicaliztion of memcpy, will be removing a couple of
> > > lines of code. I am not sure about the size of backend changes to
> > > optimize load-store patterns. But I expect it to be small.
> >
>
> > Are you saying that the canonicalization you want to change is
> > tem...
2016 Mar 22
8
RFC: A change in InstCombine canonical form
On Tue, Mar 22, 2016 at 1:41 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
> Sorry I should have been more clear (writing to many email in parallel)
>
> You're right. I was adding a +1 to you here.
>
> Especially I wrote "unless there is an acknowledgement that typeless
> pointers won't be there before a couple of years" with the PassManager in
>