X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Date:	Sun, 09 Jan 2005 12:35:03 -0700
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject:	Re: restrict keyword
In-reply-to:	<200501091459.j09ExiLO022171@speedy.ludd.ltu.se>
To:	djgpp-workers AT delorie DOT com
Message-id:	<po13u0d5utt13bu5po82aqt9ckvvfv1bne@4ax.com>
Organization:	Systematic Software
MIME-version:	1.0
X-Mailer:	Forte Agent 1.93/32.576 English (American)
References:	<q8cmt0p9e3ri4p17udh3lvk1gdrfoclb31 AT 4ax DOT com>
	<200501091459 DOT j09ExiLO022171 AT speedy DOT ludd DOT ltu DOT se>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j09JZ6Ut014610
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

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. 

-- 
Thanks. Take care, Brian Inglis

- Raw text -