public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/30363] [4.2 Regression] Support for -traditional-cpp is incomplete in current gcc relative to gcc 2.95.3 Date: Mon, 30 Mar 2009 20:21:00 -0000 [thread overview] Message-ID: <20090330202123.16346.qmail@sourceware.org> (raw) In-Reply-To: <bug-30363-9863@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from jsm28 at gcc dot gnu dot org 2009-03-30 20:21 ------- Closing 4.2 branch, fixed in 4.3. -- jsm28 at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Known to fail|3.3.3 3.4.0 4.0.0 4.1.0 |3.3.3 3.4.0 4.0.0 4.1.0 |4.2.0 4.0.4 4.1.2 4.1.1 |4.2.0 4.0.4 4.1.2 4.1.1 |4.1.0 4.0.4 4.0.3 4.0.2 |4.1.0 4.0.4 4.0.3 4.0.2 |4.0.1 |4.0.1 4.2.5 Resolution| |FIXED Target Milestone|4.2.5 |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30363
prev parent reply other threads:[~2009-03-30 20:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-04 3:24 [Bug preprocessor/30363] New: " fnf at specifixinc dot com 2007-01-07 1:09 ` [Bug preprocessor/30363] [4.0/4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org 2007-01-07 1:21 ` fnf at specifixinc dot com 2007-02-03 21:23 ` gdr at gcc dot gnu dot org 2007-02-03 21:24 ` pinskia at gcc dot gnu dot org 2007-02-05 5:49 ` mmitchel at gcc dot gnu dot org 2007-02-14 9:20 ` mmitchel at gcc dot gnu dot org 2007-12-16 23:19 ` steven at gcc dot gnu dot org 2007-12-18 4:09 ` tromey at gcc dot gnu dot org 2008-01-07 17:30 ` tromey at gcc dot gnu dot org 2008-01-07 17:34 ` [Bug preprocessor/30363] [4.0/4.1/4.2 " tromey at gcc dot gnu dot org 2008-07-04 21:48 ` [Bug preprocessor/30363] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-30 20:21 ` jsm28 at gcc dot gnu dot org [this message]
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=20090330202123.16346.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: 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).