public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61412] Warnings incorrectly suppressed when compiling previously preprocessed file
Date: Wed, 04 Jun 2014 15:34:00 -0000	[thread overview]
Message-ID: <bug-61412-4-womR9xEgtJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61412-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61412

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Matt Godbolt from comment #0)
> --begin example
> # 88 "some/file.cpp" 3 4
> struct Foo { int i, j; Foo() : j(1), i(0) {} };
> --end example

How did you produce that file?  If you compile the exact preprocessor output
you shouldn't have a problem. If you mangle it, fooling the compiler into
thinking it's in a system header, you have a problem.


  parent reply	other threads:[~2014-06-04 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 14:52 [Bug c++/61412] New: " matt at godbolt dot org
2014-06-04 15:31 ` [Bug c++/61412] " redi at gcc dot gnu.org
2014-06-04 15:33 ` matt at godbolt dot org
2014-06-04 15:34 ` redi at gcc dot gnu.org [this message]
2014-06-04 15:51 ` matt at godbolt dot org
2014-06-04 15:52 ` schwab@linux-m68k.org
2014-06-04 16:31 ` redi at gcc dot gnu.org
2014-06-04 17:10 ` redi at gcc dot gnu.org
2014-06-04 17:28 ` matt at godbolt dot org

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=bug-61412-4-womR9xEgtJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).