This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH to implement `restrict' in C
- To: egcs-patches at cygnus dot com
- Subject: Re: PATCH to implement `restrict' in C
- From: Ulrich Drepper <drepper at cygnus dot com>
- Date: 14 Oct 1998 12:53:55 -0700
- Newsgroups: cygnus.egcs.patches
- Organization: Cygnus Solutions
- References: <199810092015.NAA13687@smtp.earthlink.net>, <9531.908385347.cygnus.egcs.patches@hurl.cygnus.com>
- Reply-To: drepper at cygnus dot com (Ulrich Drepper)
law@cygnus.com (Jeffrey A Law) writes:
> I'm not sure we want a -f option to control restrict. I think we're
> better off with an option that enables isoc9x features, instead of
> controlling each one separately.
I've not yet finished my patch for this but hopefully will sometime
soon. Until the C variant selection is possible we can live with the
usual __*__ variant of the name.
> I think this would be a serious limitation, in the light of C9X
> compliance. When I read the draft right
>
> struct foo{
> struct foo * restrict next;
> int value;
> };
It's indeed necesary to support restrict as a type qualifier in the
same way as volatile and const are handled. Says ISO C 9x.
For C++: I thinke it would help a lot.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------