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 16:31:00 -0000	[thread overview]
Message-ID: <bug-61412-4-ksopnw6clY@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 #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
cat > sys/h.h <<EOT
#define X(I) char c = { I }
EOT
cat > C.C << EOT
#include <h.h>
int main () {
  int i = 256;
  X(i);
}
EOT
g++ -isystem sys C.C -Wall
g++ -isystem sys C.C -Wall -Wsystem-headers
In file included from C.C:1:0:
C.C: In function ‘int main()’:
C.C:4:3: warning: narrowing conversion of ‘i’ from ‘int’ to ‘char’ inside { }
is ill-formed in C++11 [-Wnarrowing]
   X(i);
   ^
>From gcc-bugs-return-453227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 04 17:04:31 2014
Return-Path: <gcc-bugs-return-453227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2047 invoked by alias); 4 Jun 2014 17:04:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2021 invoked by uid 48); 4 Jun 2014 17:04:26 -0000
From: "matt at godbolt dot 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 17:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matt at godbolt dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61412-4-v4ofJoAAHx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-06/txt/msg00309.txt.bz2
Content-length: 842

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida412

--- Comment #12 from Matt Godbolt <matt at godbolt dot org> ---
I appreciate your patience on this! I'm also now confused.  My 250k+
preprocessed file does not warn on a reordered constructor initializer, despite
there being no system code or macros involved in it.  Compiling the original
file (not the preprocessed version) directly warns as expected.

While attempting the reduce to an absolute minimal case I found the (or maybe
just one) issue that caused the suppression of the warning was the "#" line.
This is many hundreds of lines above the constructor and its initializer and is
unconnected to a system include.

The "#" line itself refers only to a non-system file, which confuses me.

I will try and get a non-preprocessed reproducible case to try and clear up any
confusion.


  parent reply	other threads:[~2014-06-04 16:31 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
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 [this message]
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-ksopnw6clY@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).