This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Implementing "restrict", and other alias questions
- To: Martin von Loewis <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Subject: Re: Implementing "restrict", and other alias questions
- From: Richard Henderson <rth at cygnus dot com>
- Date: Sun, 28 Dec 1997 15:12:44 -0800
- Cc: jfc at tiac dot net, egcs at cygnus dot com
- References: <199712280112.UAA01060@jfc.> <199712282017.VAA06137@mira.isdn.cs.tu-berlin.de>
- Reply-To: Richard Henderson <rth at cygnus dot com>
On Sun, Dec 28, 1997 at 09:17:37PM +0100, Martin von Loewis wrote:
> struct foo{
> struct foo * restrict next;
> int value;
> };
>
> Again, the implementation is free to ignore the declaration - it
> should not reject it.
I agree that this is the proper attitude to take.
> Another issue is references: Is
>
> void f(class C restrict &);
>
> valid. If so, how does restrict interfere with function overloading?
In the same way that `register' interferes, that is, not at all.
r~