public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: fredette@mit.edu, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: preprocessor/4976: cpp fails to warn about macro redefinitions
Date: Thu, 22 Nov 2001 20:36:00 -0000	[thread overview]
Message-ID: <20011130230309.10997.qmail@sourceware.cygnus.com> (raw)

Synopsis: cpp fails to warn about macro redefinitions

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Fri Nov 30 15:03:08 2001
State-Changed-Why:
    Please don't mark PRs as high priority; that is supposed to
    be reserved for GCC maintainers.
    
    GCC has been fixed to emit the warning in 3.0.3 and 3.1.
    3.0.2 only warns if -pedantic.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4976&database=gcc


             reply	other threads:[~2001-11-30 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 20:36 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-23  0:46 neil
2001-11-23  0:45 Neil Booth
2001-11-22 14:26 fredette

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=20011130230309.10997.qmail@sourceware.cygnus.com \
    --to=neil@gcc.gnu.org \
    --cc=fredette@mit.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).