[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem in Tru64 with autoconf choosen cc flags [PATCH]

From: Nicolás Lichtmaier
Subject: Re: Problem in Tru64 with autoconf choosen cc flags [PATCH]
Date: Thu, 15 Jan 2004 10:48:25 -0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3

Paul Eggert wrote:

So it seems to me that the retionale for definining __STDC__ to 0 is:
"We allow code which is not strictly ANSI in this mode". This is also
true for the normal gcc mode!

That is a bug in GCC that should be fixed.  I fixed it long ago for
GCC on Solaris: ot defines __STDC__ to be 1 in user code (though it is
still 0 in system headers, since that's what the Solaris system
headers want).

But if -std doesn't handle \x in strings, then it's not upward
compatible with C89, so it still seems to me that -std1 would
be more appropriate.

What exactly does -std1 disable?  Why is it bad to use -std1?
The configure test for ansi-ness recognizes -std as an ANSI mode. In fact:

$ cat test.c
int main()
       printf("%d\n", '\x00');
$ cc -o test test.c
$ cc -std -o test test.c
$ cc -std1 -o test test.c

Nicolás Lichtmaier.-
Synapsis Argentina
+54(11)4314-3000 (int. 231)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]