On Wed, 2017-04-26 at 20:52 +0200, Richard Biener wrote:
>
> I'll throw it on x86 testing and will commit it. What branches are
> affected? Can you open a bugreport?
>
> I'll try to add a runtime testcase as well if you don't beat me to
> that. On x86 it likely requires -fschedule-insns to tri
On April 26, 2017 8:03:44 PM GMT+02:00, Steve Ellcey wrote:
>On Wed, 2017-04-26 at 11:33 +0200, Richard Biener wrote:
>> >
>> > Index: gcc/emit-rtl.c
>> > ===
>> > --- gcc/emit-rtl.c (revision 247273)
>> > +++ gcc/emit-rtl.c
On Wed, 2017-04-26 at 11:33 +0200, Richard Biener wrote:
> >
> > Index: gcc/emit-rtl.c
> > ===
> > --- gcc/emit-rtl.c (revision 247273)
> > +++ gcc/emit-rtl.c (working copy)
> > @@ -1954,7 +1954,10 @@ set_mem_attributes_minu
On Wed, Apr 26, 2017 at 11:27 AM, Richard Biener
wrote:
> On Wed, Apr 26, 2017 at 12:27 AM, Steve Ellcey wrote:
>> This patch changes get_ref_base_and_extent to treat zero sized arrays
>> like C99 flexible arrays and assume that references to zero sized
>> arrays can also be made beyond the 'end'
On Wed, Apr 26, 2017 at 12:27 AM, Steve Ellcey wrote:
> This patch changes get_ref_base_and_extent to treat zero sized arrays
> like C99 flexible arrays and assume that references to zero sized
> arrays can also be made beyond the 'end' of the array. C99 flexible
> arrays are recognized by not ha
This patch changes get_ref_base_and_extent to treat zero sized arrays
like C99 flexible arrays and assume that references to zero sized
arrays can also be made beyond the 'end' of the array. C99 flexible
arrays are recognized by not having an INTEGER_CST limit/size and the
routine then sets maxsiz
