This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/71517] g++ gives different warnings if compiling a file directly or adding preprocess step
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 13 Jun 2016 10:57:58 +0000
- Subject: [Bug c++/71517] g++ gives different warnings if compiling a file directly or adding preprocess step
- Auto-submitted: auto-generated
- References: <bug-71517-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71517
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Preprocessing loses macro invocation context information, so such differences
are expected (use -Wsystem-headers if you want to see warnings regardless if
something comes from system headers or not, or better preprocess just with -E
-fdirectives-only so that such information is not lost).