Date:	Sun, 26 Mar 2000 01:12:00 -0500
Message-Id:	<200003260612.BAA29293@mescaline.gnu.org>
From:	Eli Zaretskii <eliz AT gnu DOT org>
To:	djgpp-workers AT delorie DOT com
In-reply-to:	<200003241507.QAA28898@lws256.lu.erisoft.se> (message from Martin
	Stromberg on Fri, 24 Mar 2000 16:07:01 +0100 (MET))
Subject:	Re: restrict
References:	<200003241507 DOT QAA28898 AT lws256 DOT lu DOT erisoft DOT se>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

   How should we handle the new keyword restrict, until GCC supports it?

I imagine you checked this, but I'm surprised: I thought GCC 2.95.x
already supported `restrict'.  Perhaps it's a good idea to ask on
gnu.gcc.bug.

   (The C99 standard sprinkles them everywhere in the headers, even in
   old headers.) "#define restrict" somewhere strategically?

The GCC maintainers might have a better suggestion.  I'd guess we are
not the only ones who bumped into this; glibc probably did that a long
time ago.

- Raw text -