X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Date: Wed, 12 Jan 2005 21:51:10 -0700 From: Brian Inglis Subject: Re: restrict keyword In-reply-to: To: djgpp-workers AT delorie DOT com Message-id: Organization: Systematic Software MIME-version: 1.0 X-Mailer: Forte Agent 1.93/32.576 English (American) Content-type: text/plain; charset=us-ascii References: <200501091459 DOT j09ExiLO022171 AT speedy DOT ludd DOT ltu DOT se> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j0D4ptcd001948 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 09 Jan 2005 12:35:03 -0700, Brian Inglis wrote: >On Sun, 09 Jan 2005 15:59:44 +0100 (CET), ams AT ludd DOT ltu DOT se wrote: > >>> >According to Brian Inglis: >>> >> I'd suggest one or more underscores _restrict or _RESTRICT_ or >>> >> __restrict__. >> >>Oh yes. When I use __restrict__ there are no complaints from gcc, so >>we can forget about this: >> >>> >+#if __GNUC__ < 3 || __GNUC__ == 3 && __GNUC_MINOR__ < what!!!! >>> >#define __restrict__ >>... >>> >#endif > >We still need that code if we are going to support gcc versions >earlier than whenever __restrict__ was added. Anyone know (how to find out) in which version of gcc the patch in the message below was included? http://gcc.gnu.org/ml/gcc-patches/1998-10/msg00356.html -- Thanks. Take care, Brian Inglis