From: Neil Booth <neil@daikokuya.co.uk>
To: gcc@gcc.gnu.org
Subject: [RFC] __extension__ and warnings
Date: Wed, 11 Dec 2002 14:16:00 -0000 [thread overview]
Message-ID: <20021211215751.GA5481@daikokuya.co.uk> (raw)
I've been looking into PR 7263 about __extension__ not turning off
warnings about LL and ULL.
Not surprisingly, our treatment of warn_long_long is quite inconsistent
within front ends, and with cpplib, and with use of __extension__.
Getting things 100% right with __extension__ is hard, and would uglify
the parsers further. I don't think the pain is worth the gain, and I
don't want to go there. At present we turn of pedantic, warn_traditional,
warn_pointer_arith and flag_iso in the C front end, and pedantic in the
C++ front end.
I propose a simpler solution: simply do not emit any pedwarns whilst inside
the code affected by __extension__. This is easy to implement inside
pedwarn() itself.
With this, I can clear up some confused and confusing warning logic, and fix
its interaction with cpplib's number interpreter. Thoughts?
Neil.
next reply other threads:[~2002-12-11 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 14:16 Neil Booth [this message]
2002-12-11 14:19 ` Gabriel Dos Reis
2002-12-11 22:55 ` Mark Mitchell
2002-12-11 15:17 ` Zack Weinberg
2002-12-11 15:54 ` Neil Booth
2002-12-11 23:54 ` Neil Booth
2002-12-11 23:58 ` Gabriel Dos Reis
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=20021211215751.GA5481@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=gcc@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).