public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <E15AyCQ-0001Fh-00@bombur.uio.no> (raw) >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:
next reply other threads:[~2001-06-15 11:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-15 11:26 h.b.furuseth [this message] 2001-06-16 0:16 neil
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=E15AyCQ-0001Fh-00@bombur.uio.no \ --to=h.b.furuseth@usit.uio.no \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).