On Fri, 7 Apr 2017, Rainer Orth wrote:
> Hi Richard,
>
> >> > Any suggestion how to mitigate that? Possible solution includes
> >> > adding { target { ! ... } } to dg-do run.
> >>
> >> No idea. However, according to gcc-testresults there are other
> >> failures: s390-ibm-inux-gnu and s390x-ibm
Hi Richard,
>> > Any suggestion how to mitigate that? Possible solution includes
>> > adding { target { ! ... } } to dg-do run.
>>
>> No idea. However, according to gcc-testresults there are other
>> failures: s390-ibm-inux-gnu and s390x-ibm-linux-gnu so far.
>>
>> This might argue against jus
On Fri, 7 Apr 2017, Rainer Orth wrote:
> Hi Richard,
>
> > On Thu, 6 Apr 2017, Rainer Orth wrote:
> >
> >> Hi Richard,
> >>
> >> > The following patch makes sure to preserve (mis-)alignment of memory
> >> > references when IVOPTs generates TARGET_MEM_REFs for them.
> >> >
> >> > Bootstrapped on
Hi Richard,
> On Thu, 6 Apr 2017, Rainer Orth wrote:
>
>> Hi Richard,
>>
>> > The following patch makes sure to preserve (mis-)alignment of memory
>> > references when IVOPTs generates TARGET_MEM_REFs for them.
>> >
>> > Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>> >
>> > Ric
On Thu, 6 Apr 2017, Rainer Orth wrote:
> Hi Richard,
>
> > The following patch makes sure to preserve (mis-)alignment of memory
> > references when IVOPTs generates TARGET_MEM_REFs for them.
> >
> > Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
> >
> > Richard.
> >
> > 2017-04-06
Hi Richard,
> The following patch makes sure to preserve (mis-)alignment of memory
> references when IVOPTs generates TARGET_MEM_REFs for them.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>
> Richard.
>
> 2017-04-06 Richard Biener
>
> PR tree-optimization/80334
>
The following patch makes sure to preserve (mis-)alignment of memory
references when IVOPTs generates TARGET_MEM_REFs for them.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2017-04-06 Richard Biener
PR tree-optimization/80334
* tree-ssa-loop-ivopts
