On 11/25/2016 01:04 AM, Richard Biener wrote:
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
Richard Biener writes:
On Thu, 24 Nov 2016, Richard Biener wrote:
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
Hi,
I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
>
> Richard Biener writes:
>
> > On Thu, 24 Nov 2016, Richard Biener wrote:
> >
> >> On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
> >>
> >> > Hi,
> >> >
> >> > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the
> >>
Richard Biener writes:
> On Thu, 24 Nov 2016, Richard Biener wrote:
>
>> On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
>>
>> > Hi,
>> >
>> > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr
>> > target. I found that the (dump) failure is because there are 4
>>
On Thu, 24 Nov 2016, Richard Biener wrote:
> On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
>
> > Hi,
> >
> > I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr
> > target. I found that the (dump) failure is because there are 4
> > instances of memcpy, while the
On Thu, 24 Nov 2016, Senthil Kumar Selvaraj wrote:
> Hi,
>
> I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr
> target. I found that the (dump) failure is because there are 4
> instances of memcpy, while the testcase expects only 2 for a
> non-strict align target
Hi,
I've been analyzing a failing regtest (gcc.dg/strlenopt-8.c) for the avr
target. I found that the (dump) failure is because there are 4
instances of memcpy, while the testcase expects only 2 for a
non-strict align target like the avr.
Comparing that with a dump generated by