From mboxrd@z Thu Jan  1 00:00:00 1970
From: h.b.furuseth@usit.uio.no
To: gcc-gnats@gcc.gnu.org
Subject: other/3199: Wrong expansion of __STRICT_ANSI__ in cpp.texi
Date: Fri, 15 Jun 2001 11:26:00 -0000
Message-id: <E15AyCQ-0001Fh-00@bombur.uio.no>
X-SW-Source: 2001-06/msg00680.html
List-Id: <gcc-prs.sourceware.org>

>Number:         3199
>Category:       other
>Synopsis:       Wrong expansion of __STRICT_ANSI__ in cpp.texi
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 15 11:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Hallvard B Furuseth
>Release:        3.0 20010611 (prerelease)
>Organization:
University of Oslo
>Environment:
System: SunOS bombur.uio.no 5.8 Generic_108528-03 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4

	
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: ./configure --quiet
>Description:
	cpp.texi, @item __STRICT_ANSI__, says:
		Its definition is the null string.
	However, `gcc -ansi' defines `__STRICT_ANSI__' as `1'.

>How-To-Repeat:
	$ echo '[__STRICT_ANSI__]' | ./xgcc -B./ -E -P -ansi -xc -
	[1]
>Fix:
	If -ansi did set __STRICT_ANSI__ to `' in the past, the best
	fix is probably to remove the offending sentence instead of
	correcting it, for backwards compatibility.
>Release-Note:
>Audit-Trail:
>Unformatted: