From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200004232143.XAA24489@father.ludd.luth.se>
Subject: restrict
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Sun, 23 Apr 2000 23:43:12 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

According the the gcc manual restrict is only available if
"-flang-isoc9x" option is given to gcc. And that seems to be a
documentation bug, you need to use "-std=iso9899:199x according to
<http://gcc.gnu.org/ml/gcc-bugs/1999-11n/msg00793.html>.

So I sueggest we use __restrict__ instead of restrict which seems to
be recognised always (I guess, from the documentation).

So how far back was __restrict__ supported? Or can we demand that
users of DJGPP v. 2.04 use gcc 2.95.2? I can't check what gcc 2.8.1
does as I've upgraded to gcc 2.95.2 and the archives of 2.8.1 is not
left on (the mirror of) simtel.net.

Or do you know/suggest a different approach (some magic #define
somewhere, perhaps)?


Right,

							MartinS