This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: bug 2645 and restrict

To: Gabriel Dos Reis <gdr at codesourcery dot com>
Subject: Re: bug 2645 and restrict
From: Jason Merrill <jason_merrill at redhat dot com>
Date: 27 Apr 2001 02:00:49 +0100
Cc: Nathan Sidwell <nathan at codesourcery dot com>, gcc at gcc dot gnu dot org, mark at codesourcery dot com
References: <3AE7E5AB.6371CD8B@codesourcery.com><m3bspjk872.fsf@prospero.cambridge.redhat.com><flu23by758.fsf@sel.cmla.ens-cachan.fr>

>>>>> "Gabriel" == Gabriel Dos Reis <gdr@codesourcery.com> writes:

> I don't agree. The description given by Nathan applies as well to
> volatile.

I agree with Fergus that this is unfortunate.  But I suppose I'd be happy
to accept __restrict__ in this situation with a warning.

>>>>> "Alexandre" == Alexandre Oliva <aoliva@redhat.com> writes:
> On Apr 26, 2001, Jason Merrill <jason_merrill@redhat.com> wrote:

>> __restrict__ implies a property which only pointers can have

> references might be decorated with __restrict__ too, I suppose.

Yes, I meant pointers or references.

Jason

Follow-Ups:
- Re: bug 2645 and restrict
  - From: Mark Mitchell

References:
- bug 2645 and restrict
  - From: Nathan Sidwell
- Re: bug 2645 and restrict
  - From: Jason Merrill
- Re: bug 2645 and restrict
  - From: Gabriel Dos Reis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]