public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65040] [5 Regression] gcc-5 -Wformat broken
Date: Thu, 12 Feb 2015 11:07:00 -0000 [thread overview]
Message-ID: <bug-65040-4-kaSI2p6Owp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65040-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65040
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #2)
> Taking. I think check_format_types needs a small tweak to look thru
> NOP_EXPRs.
Well, more like do some lame VR computation and not warn if the signedness
doesn't really matter.
next prev parent reply other threads:[~2015-02-12 11:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 10:10 [Bug c/65040] New: " rguenth at gcc dot gnu.org
2015-02-12 10:10 ` [Bug c/65040] " rguenth at gcc dot gnu.org
2015-02-12 10:37 ` mpolacek at gcc dot gnu.org
2015-02-12 10:46 ` mpolacek at gcc dot gnu.org
2015-02-12 11:05 ` jakub at gcc dot gnu.org
2015-02-12 11:07 ` jakub at gcc dot gnu.org [this message]
2015-02-12 11:12 ` mark at gcc dot gnu.org
2015-02-12 11:33 ` fche at redhat dot com
2015-02-13 7:56 ` mpolacek at gcc dot gnu.org
2015-02-13 7:57 ` mpolacek at gcc dot gnu.org
2015-02-14 9:58 ` jirislaby at gmail dot com
2015-02-14 10:31 ` mpolacek at gcc dot gnu.org
2015-02-14 11:21 ` jakub at gcc dot gnu.org
2015-02-14 11:21 ` jirislaby at gmail dot com
2015-02-16 11:17 ` mpolacek at gcc dot gnu.org
2015-02-24 9:40 ` rguenth at gcc dot gnu.org
2015-02-24 9:57 ` rguenth at gcc dot gnu.org
2015-02-24 10:14 ` mpolacek at gcc dot gnu.org
2015-02-24 10:16 ` jakub at gcc dot gnu.org
2015-02-24 10:22 ` rguenth at gcc dot gnu.org
2015-02-27 15:02 ` mpolacek at gcc dot gnu.org
2015-02-27 15:03 ` mpolacek at gcc dot gnu.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-65040-4-kaSI2p6Owp@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).