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: ak at muc dot de
- Subject: Re: PATCH to implement `restrict' in C
- From: Mark Mitchell <mark at markmitchell dot com>
- Date: Tue, 20 Oct 1998 09:06:56 -0700
- CC: law at cygnus dot com, egcs-patches at cygnus dot com
- References: <17225.908849307@upchuck> <k23e8jsb68.fsf@zero.aec.at>
- Reply-to: mark at markmitchell dot com
>>>>> "Andi" == Andi Kleen <ak@muc.de> writes:
Andi> In article <17225.908849307@upchuck>, Jeffrey A Law
Andi> <law@cygnus.com> writes:
>>> OK. I'll change the spelling of -frestrict to -fisoc9x, and
>>> alter the documentation accordingly. If there are other c9x
>>> features (like _Pragma) implemented, they can go under this
>>> flag.
>> I'd make it a -lang-c9x to be consistent with other options
>> which control language dialects.
Andi> There is one problem with that: once restrict is ported to
Andi> g++ it will need an own option for it. -flang-c9x doesn't
Nope. There will be no `restrict' in g++; only `__restrict__'. If at
some point a new C++ standard introduces `restrict' in C++, we will
have a name for all the other new features introduced by that standard,
like -flang-cxx2005. We can use `__restrict__' since it is reserved
for the implementation.
--
Mark Mitchell mark@markmitchell.com
Mark Mitchell Consulting http://www.markmitchell.com