public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tmsriram at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53661] [gcc-4.7/4.8 regression] Wrong narrowing conversion warning with -std=c++11 Date: Tue, 07 Aug 2012 22:34:00 -0000 [thread overview] Message-ID: <bug-53661-4-UGT9bOHMoU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53661-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53661 Sriraman Tallam <tmsriram at google dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c |c++ Summary|Wrong narrowing conversion |[gcc-4.7/4.8 regression] |warning with -std=c++11 |Wrong narrowing conversion | |warning with -std=c++11 --- Comment #1 from Sriraman Tallam <tmsriram at google dot com> 2012-08-07 22:33:58 UTC --- Tip of trunk still fails.
next prev parent reply other threads:[~2012-08-07 22:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 20:42 [Bug c/53661] New: " tmsriram at google dot com 2012-08-07 22:34 ` tmsriram at google dot com [this message] 2012-09-13 23:40 ` [Bug c++/53661] [gcc-4.7/4.8 regression] " paolo.carlini at oracle dot com 2012-09-13 23:43 ` paolo.carlini at oracle dot com 2012-09-14 6:05 ` manu at gcc dot gnu.org 2012-09-14 9:37 ` paolo.carlini at oracle dot com 2012-09-14 13:46 ` jason at gcc dot gnu.org 2012-09-14 13:49 ` paolo.carlini at oracle dot com 2012-09-14 14:07 ` manu at gcc dot gnu.org 2012-09-14 16:28 ` harald at gigawatt dot nl 2012-09-17 15:42 ` jason at gcc dot gnu.org 2012-09-17 16:06 ` jason at gcc dot gnu.org 2012-09-17 16:25 ` harald at gigawatt dot nl 2012-09-17 16:42 ` jason at gcc dot gnu.org 2012-09-17 16:42 ` jason at gcc dot gnu.org 2012-09-17 16:43 ` jason 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-53661-4-UGT9bOHMoU@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: linkBe 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).