public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57241] -Wmultichar warnings despite a #pragma diagnostic ignored -Wmultichar directive
Date: Sat, 16 Nov 2013 20:23:00 -0000 [thread overview]
Message-ID: <bug-57241-4-oAHbLIidZT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57241-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57241
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #4)
>
> Doesn't CPP diagnostics pass through the pragma classify code in
> diagnostic.c even when tokenizing ahead of time? If so, I don't understand
> why the warning is not suppressed. I don't have time to investigate it
> myself, but I don't see why that would be the problem here.
So answering to myself: No, it doesn't (see PR53431). I think it must.
This affects all the controllable warnings from CPP when using g++.
*** This bug has been marked as a duplicate of bug 53431 ***
>From gcc-bugs-return-434771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 16 20:32:50 2013
Return-Path: <gcc-bugs-return-434771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31297 invoked by alias); 16 Nov 2013 20:32:50 -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 31273 invoked by uid 48); 16 Nov 2013 20:32:47 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59156] code miscompiled with -O2 -fpeel-loops
Date: Sat, 16 Nov 2013 20:32: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.7.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.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-59156-4-ta1xMRsyV3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59156-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: 2013-11/txt/msg01548.txt.bz2
Content-length: 150
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY156
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
-fno-strict-aliasing fixes it.
prev parent reply other threads:[~2013-11-16 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 16:41 [Bug c++/57241] New: GCC still issues " scottbaldwin at gmail dot com
2013-05-10 16:49 ` [Bug c++/57241] " paolo.carlini at oracle dot com
2013-05-10 16:57 ` pinskia at gcc dot gnu.org
2013-05-10 17:23 ` scottbaldwin at gmail dot com
2013-05-12 20:08 ` [Bug c++/57241] " manu at gcc dot gnu.org
2013-11-16 20:23 ` manu at gcc dot gnu.org [this message]
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-57241-4-oAHbLIidZT@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).