public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/65316] [5 Regression] LTO: Uninitialized memory / ICE with -g -fno-lto-odr-type-merging: in types_same_for_odr, at ipa-devirt.c:465 Date: Sat, 07 Mar 2015 20:34:00 -0000 [thread overview] Message-ID: <bug-65316-4-e1kkS8C8mm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65316 --- Comment #11 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Author: hubicka Date: Sat Mar 7 20:33:58 2015 New Revision: 221258 URL: https://gcc.gnu.org/viewcvs?rev=221258&root=gcc&view=rev Log: PR ipa/65316 * tree.c (free_lang_data_in_type): Be sure to keep BINFO_VTABLE when outputting debug. Modified: trunk/gcc/ChangeLog trunk/gcc/tree.c
next prev parent reply other threads:[~2015-03-07 20:34 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-04 18:54 [Bug lto/65316] New: " burnus at gcc dot gnu.org 2015-03-04 19:47 ` [Bug lto/65316] " trippels at gcc dot gnu.org 2015-03-05 0:01 ` hubicka at gcc dot gnu.org 2015-03-05 9:20 ` rguenth at gcc dot gnu.org 2015-03-06 6:02 ` hubicka at gcc dot gnu.org 2015-03-06 9:30 ` burnus at gcc dot gnu.org 2015-03-06 9:34 ` trippels at gcc dot gnu.org 2015-03-06 16:02 ` hubicka at gcc dot gnu.org 2015-03-06 18:25 ` hubicka at gcc dot gnu.org 2015-03-06 23:31 ` hubicka at ucw dot cz 2015-03-07 18:40 ` hubicka at gcc dot gnu.org 2015-03-07 20:34 ` hubicka at gcc dot gnu.org [this message] 2015-03-09 0:29 ` hubicka at gcc dot gnu.org 2015-03-09 1:40 ` hubicka 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-65316-4-e1kkS8C8mm@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).