X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Sat, 01 Jan 2005 12:05:56 +0200
From: "Eli Zaretskii" <eliz AT gnu DOT org>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-ID: <01c4efe9$Blat.v2.2.2$a1c24b60@zahav.net.il>
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 2.2.2
In-reply-to: <200501010100.j0110Pn3018964@speedy.ludd.ltu.se>
	(ams AT ludd DOT ltu DOT se)
Subject: Re: restrict keyword
References:  <200501010100 DOT j0110Pn3018964 AT speedy DOT ludd DOT ltu DOT se>
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

> From: <ams AT ludd DOT ltu DOT se>
> Date: Sat, 1 Jan 2005 02:00:25 +0100 (CET)
> 
> Ok.  So I replace all restrict with __restrict__ and change the
> version entry to 
> 
> +#if __GNUC__ < 3 || __GNUC__ == 3 && __GNUC_MINOR__ < what!!!!
> #define __restrict__
> else
> #define __restrict__ restrict
> #endif
> 
> ?

Yes, and I'd suggest to #undef __restrict__ at the end of the header
that defines it.  That way, we don't pollute the code with
__restrict__ even though such macros are reserved for implementation.