public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65858] [5/6 Regression] ICE in varpool_node::get_constructor during chromium build on arm-linux-gnueabihf with LTO during LINK chrome Date: Fri, 01 May 2015 18:44:00 -0000 [thread overview] Message-ID: <bug-65858-4-LjcIuams58@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65858 --- Comment #5 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> --- Author: paolo Date: Fri May 1 18:43:40 2015 New Revision: 222699 URL: https://gcc.gnu.org/viewcvs?rev=222699&root=gcc&view=rev Log: /cp 2015-05-01 Paolo Carlini <paolo.carlini@oracle.com> Prathamesh Kulharni <prathamesh.kulkarni@linaro.org> PR c++/65858 * typeck2.c (check_narrowing): Set ok = true when pedwarn returns false. /testsuite 2015-05-01 Paolo Carlini <paolo.carlini@oracle.com> Prathamesh Kulharni <prathamesh.kulkarni@linaro.org> PR c++/65858 * g++.dg/cpp0x/Wnarrowing4.C: New. Added: trunk/gcc/testsuite/g++.dg/cpp0x/Wnarrowing4.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/typeck2.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-05-01 18:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65858-4@http.gcc.gnu.org/bugzilla/> 2015-04-23 16:37 ` [Bug ipa/65858] " hubicka at gcc dot gnu.org 2015-04-27 15:47 ` prathamesh3492 at gcc dot gnu.org 2015-04-30 16:22 ` prathamesh3492 at gcc dot gnu.org 2015-04-30 19:48 ` [Bug c++/65858] [5/6 Regression] " paolo.carlini at oracle dot com 2015-05-01 18:44 ` paolo at gcc dot gnu.org [this message] 2015-05-01 18:48 ` paolo at gcc dot gnu.org 2015-05-01 18:55 ` paolo.carlini at oracle dot com 2015-05-01 22:00 ` prathamesh3492 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-65858-4-LjcIuams58@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).