Hi!
Pascal Cuoq communicated to me the following example:
int ar1(int (*p)[3], int (*q)[3])
{
(*p)[0] = 1;
(*q)[1] = 2;
return (*p)[0];
}
gcc of versions 4.9.2 and 7.0.0 20161129 optimize it with -O2 on the
premise that elements with different indices don't alias:
:
On Wed, Nov 30, 2016 at 2:19 PM, Alexander Cherepanov
wrote:
> Hi!
>
> Pascal Cuoq communicated to me the following example:
>
> int ar1(int (*p)[3], int (*q)[3])
> {
> (*p)[0] = 1;
> (*q)[1] = 2;
> return (*p)[0];
> }
>
> gcc of versions 4.9.2 and 7.0.0 20161129 optimize it with -O2 on the
- Alexander Monakov schrieb:
> Hello,
>
> On Tue, 29 Nov 2016, Sebastian Huber wrote:
> > * env.c: Split out ICV definitions into...
> > * icv.c: ...here (new file) and...
> > * icv-device.c: ...here. New file.
> >
> > the env.c contains now only local symbols (at le
On Wed, 30 Nov 2016, Richard Biener wrote:
> but that probably shouldn't apply to array types. The idea is that
> objects of the same type cannot overlap. Maybe Joseph can clarify whether
> and array object of known size really constitutes an object in that sense.
This is one of the ambiguous c
Richard Sandiford writes:
> We have various other changes that aren't yet in the branch. The two
> main ones are:
>
> (a) Support for gather loads and scatter stores. This includes support
> for using gathers and scatters for strided loads and stores, or for
> grouped loads and stores wh
I am trying to understand the status of this bug and the patch
that fixes it. It looks like a patch was submitted and checked
in for 5.0 to fix the problem reported and I see the new
behavior caused by the patch in GCC 5.X compilers. This behavior
caused a number of issues with configures and sc
