public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: andrew@andypo.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: preprocessor/7263: __extension__ keyword doesn't suppress warning on LL or ULL constants
Date: Mon, 09 Dec 2002 15:10:00 -0000	[thread overview]
Message-ID: <20021209231018.16068.qmail@sources.redhat.com> (raw)

Synopsis: __extension__ keyword doesn't suppress warning on LL or ULL constants

State-Changed-From-To: open->analyzed
State-Changed-By: cae
State-Changed-When: Mon Dec  9 15:10:17 2002
State-Changed-Why:
    I can confirm this on recent 3.3. The warning is from the preprocessor
    where we don't know about __extension__. Maybe the fix is to just
    document this. Anyway: Category changed to preprocessor and priority
    raised to medium because this is technically a regression.

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


             reply	other threads:[~2002-12-09 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 15:10 ehrhardt [this message]
2002-12-09 15:26 Joseph S. Myers
2002-12-09 16:26 Neil Booth
2002-12-10  2:46 Christian Ehrhardt
2002-12-11 13: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=20021209231018.16068.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=andrew@andypo.net \
    --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).