On 29/09/15 10:29, Richard Biener wrote:
On Tue, 29 Sep 2015, Tom de Vries wrote:
On 22/09/15 09:49, Richard Biener wrote:
On Tue, 22 Sep 2015, Tom de Vries wrote:
Hi,
Consider this test-case:
struct ps
{
int *__restrict__ p;
};
void
f (struct ps &__restrict__ ps1)
{
*(ps1.p) =
On 22/09/15 09:49, Richard Biener wrote:
On Tue, 22 Sep 2015, Tom de Vries wrote:
Hi,
Consider this test-case:
struct ps
{
int *__restrict__ p;
};
void
f (struct ps &__restrict__ ps1)
{
*(ps1.p) = 1;
}
Atm, the restrict on p has no effect. Now, say we add a field to the struct:
On Tue, 29 Sep 2015, Tom de Vries wrote:
> On 22/09/15 09:49, Richard Biener wrote:
> > On Tue, 22 Sep 2015, Tom de Vries wrote:
> >
> > > Hi,
> > >
> > > Consider this test-case:
> > >
> > > struct ps
> > > {
> > >int *__restrict__ p;
> > > };
> > >
> > > void
> > > f (struct ps
Hi,
Consider this test-case:
struct ps
{
int *__restrict__ p;
};
void
f (struct ps &__restrict__ ps1)
{
*(ps1.p) = 1;
}
Atm, the restrict on p has no effect. Now, say we add a field to the struct:
struct ps
{
int *__restrict__ p;
int a;
};
Then the restrict on p does have the
On Tue, 22 Sep 2015, Tom de Vries wrote:
> Hi,
>
> Consider this test-case:
>
> struct ps
> {
> int *__restrict__ p;
> };
>
> void
> f (struct ps &__restrict__ ps1)
> {
> *(ps1.p) = 1;
> }
>
>
> Atm, the restrict on p has no effect. Now, say we add a field to the struct:
>
> struct ps
>
