This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/7263] __extension__ keyword doesn't suppress warning on LL or ULL constants
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Mar 2010 15:19:19 -0000
- Subject: [Bug preprocessor/7263] __extension__ keyword doesn't suppress warning on LL or ULL constants
- References: <bug-7263-1664@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #21 from tromey at gcc dot gnu dot org 2010-03-23 15:19 -------
> What is missing from this patch? Is it only the macro location tracked or the parameter expanded within the macro?
The biggest problem with the patch is that I didn't finish debugging it.
It causes regressions of various kinds -- it is pretty buggy.
There are a few FIXME comments marking known bad spots.
It tracks the "full" location of each token. So, if a given token resulted
from a macro expansion, you can determine the token's location from before the
macro expansion (which might come from another macro expansion, or a macro
definition, or be an argument to a macro invocation).
It doesn't currently handle the original location of tokens arising from
stringizing or pasting.
> Does this enable us to track macro expansions like Clang?
Yes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7263