X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: <ams AT ludd DOT ltu DOT se>
Message-Id: <200501091459.j09ExiLO022171@speedy.ludd.ltu.se>
Subject: Re: restrict keyword
In-Reply-To: <q8cmt0p9e3ri4p17udh3lvk1gdrfoclb31@4ax.com> "from Brian Inglis
 at Jan 4, 2005 05:16:57 pm"
To: djgpp-workers AT delorie DOT com
Date: Sun, 9 Jan 2005 15:59:44 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-ltu-MailScanner-Information: Please contact the ISP for more information
X-ltu-MailScanner: Found to be clean
X-MailScanner-From: ams AT 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

> >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


Right,

						MartinS