public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18502] trigraphs don't work with -std=gnu99
Date: Mon, 15 Nov 2004 15:15:00 -0000	[thread overview]
Message-ID: <20041115151549.12014.qmail@sourceware.org> (raw)
In-Reply-To: <20041115145424.18502.rwxr-xr-x@gmx.de>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-15 15:15 -------
Confirmed, the problem is either in the C front-end (which is really the code which drives the 
preprocessor library) or in the C driver part:
 /Users/pinskia/local/libexec/gcc/powerpc-apple-darwin7.6.0/4.0.0/cc1 -E -quiet -v -P -trigraphs 
-trigraphs -D__DYNAMIC__ -D__APPLE_CC__=1 - -fPIC -std=gnu99

Note how -std=gnu99 is done after -trigraphs.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|preprocessor                |c
     Ever Confirmed|                            |1
           Keywords|                            |diagnostic
   Last reconfirmed|0000-00-00 00:00:00         |2004-11-15 15:15:48
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18502


  reply	other threads:[~2004-11-15 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 14:55 [Bug preprocessor/18502] New: " rwxr-xr-x at gmx dot de
2004-11-15 15:15 ` pinskia at gcc dot gnu dot org [this message]
2004-11-15 15:51 ` [Bug c/18502] " joseph at codesourcery dot com
2005-02-01 23:29 ` [Bug c/18502] [3.3/3.4/4.0 Regression] " jsm28 at gcc dot gnu dot org
2005-05-01 10:34 ` [Bug c/18502] [3.3/3.4 " cvs-commit at gcc dot gnu dot org
2005-05-03 20:04 ` jsm28 at gcc dot gnu dot org

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=20041115151549.12014.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).