public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58678] [4.9 Regression] pykde4-4.11.2 link error (devirtualization too trigger happy) Date: Thu, 28 Aug 2014 17:11:00 -0000 [thread overview] Message-ID: <bug-58678-4-hF3scbIsCh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58678 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |ASSIGNED Resolution|FIXED |--- --- Comment #59 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Markus Trippelsdorf from comment #58) These are breaking with -flto because make_decl_local clears DECL_COMDAT, so the check I added to ipa_devirt doesn't trigger. Honza, can we just remove that from make_decl_local? It seems harmless to me to leave the flag set.
next prev parent reply other threads:[~2014-08-28 17:11 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-10 8:25 [Bug ipa/58678] New: " markus at trippelsdorf dot de 2013-10-10 8:39 ` [Bug ipa/58678] " hubicka at gcc dot gnu.org 2013-10-10 9:58 ` markus at trippelsdorf dot de 2013-10-10 10:11 ` markus at trippelsdorf dot de 2013-10-10 10:37 ` hubicka at ucw dot cz 2013-10-10 10:49 ` hubicka at gcc dot gnu.org 2014-01-21 11:57 ` nheghathivhistha at gmail dot com 2014-01-21 12:28 ` nheghathivhistha at gmail dot com 2014-01-21 12:30 ` trippels at gcc dot gnu.org 2014-01-21 12:54 ` nheghathivhistha at gmail dot com 2014-01-21 14:55 ` nheghathivhistha at gmail dot com 2014-01-21 14:59 ` trippels at gcc dot gnu.org 2014-01-21 16:23 ` nheghathivhistha at gmail dot com 2014-01-21 17:22 ` trippels at gcc dot gnu.org 2014-01-31 10:49 ` rguenth at gcc dot gnu.org 2014-01-31 11:04 ` rguenth at gcc dot gnu.org 2014-02-04 6:51 ` [Bug c++/58678] " hubicka at gcc dot gnu.org 2014-02-07 10:24 ` nheghathivhistha at gmail dot com 2014-02-17 18:51 ` hubicka at gcc dot gnu.org 2014-02-27 5:09 ` jason at gcc dot gnu.org 2014-02-28 17:28 ` hubicka at gcc dot gnu.org 2014-03-01 0:17 ` jason at gcc dot gnu.org 2014-03-01 1:58 ` jason at gcc dot gnu.org 2014-03-05 13:42 ` nheghathivhistha at gmail dot com 2014-03-05 15:02 ` trippels at gcc dot gnu.org 2014-03-05 15:11 ` trippels at gcc dot gnu.org 2014-03-05 15:58 ` jason at gcc dot gnu.org 2014-03-05 16:31 ` nheghathivhistha at gmail dot com 2014-03-05 16:48 ` trippels at gcc dot gnu.org 2014-03-05 18:28 ` jason at gcc dot gnu.org 2014-03-05 18:31 ` trippels at gcc dot gnu.org 2014-03-10 16:30 ` jason at gcc dot gnu.org 2014-03-12 19:21 ` nheghathivhistha at gmail dot com 2014-03-12 19:21 ` nheghathivhistha at gmail dot com 2014-03-14 19:07 ` jason at gcc dot gnu.org 2014-03-14 19:14 ` jason at gcc dot gnu.org 2014-03-15 1:39 ` jason at gcc dot gnu.org 2014-03-15 18:14 ` nheghathivhistha at gmail dot com 2014-03-15 21:01 ` jason at gcc dot gnu.org 2014-03-16 7:44 ` nheghathivhistha at gmail dot com 2014-03-16 7:46 ` nheghathivhistha at gmail dot com 2014-03-16 7:55 ` trippels at gcc dot gnu.org 2014-03-16 8:35 ` trippels at gcc dot gnu.org 2014-03-16 9:07 ` trippels at gcc dot gnu.org 2014-03-16 11:44 ` nheghathivhistha at gmail dot com 2014-03-16 13:17 ` nheghathivhistha at gmail dot com 2014-03-16 13:28 ` trippels at gcc dot gnu.org 2014-03-16 14:27 ` jakub at gcc dot gnu.org 2014-03-17 18:08 ` jason at gcc dot gnu.org 2014-03-17 18:21 ` trippels at gcc dot gnu.org 2014-03-17 19:17 ` nheghathivhistha at gmail dot com 2014-03-17 20:01 ` jason at gcc dot gnu.org 2014-03-17 20:16 ` jason at gcc dot gnu.org 2014-03-17 20:33 ` trippels at gcc dot gnu.org 2014-03-20 21:06 ` jason at gcc dot gnu.org 2014-03-21 10:34 ` jakub at gcc dot gnu.org 2014-03-26 16:51 ` jason at gcc dot gnu.org 2014-03-28 17:18 ` jakub at gcc dot gnu.org 2014-08-28 17:11 ` jason at gcc dot gnu.org [this message] 2014-08-29 10:33 ` trippels at gcc dot gnu.org 2014-08-29 16:13 ` jason at gcc dot gnu.org 2014-08-29 19:00 ` jason at gcc dot gnu.org 2014-08-29 19:19 ` trippels at gcc dot gnu.org 2014-08-29 19:38 ` jason at gcc dot gnu.org 2014-09-09 11:32 ` trippels at gcc dot gnu.org 2014-09-11 12:12 ` jason at gcc dot gnu.org 2014-09-11 12:13 ` jason at gcc dot gnu.org 2014-09-11 12:16 ` 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-58678-4-hF3scbIsCh@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).