public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65276] [5 Regression] LTO: ICE add_type_duplicate, at ipa-devirt.c:1462
Date: Mon, 02 Mar 2015 17:47:00 -0000	[thread overview]
Message-ID: <bug-65276-4-TlJ6eVzRHO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65276-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65276

--- Comment #4 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #3)
> I guess it is the case where one type come from -O0 unit and have no
> TYPE_BINFO, because it is not optimized. I think just removing the check may
> work these days - I changed the way leading candidate is chosen and it
> should be one with BINFO after all.

Correct, TYPE_BINFO(type2) is NULL.

Started with:

commit 87a9c1b6624ae11321799e7c9aba4a7b47567d5d
Author: hubicka <hubicka@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Mon Feb 9 20:34:18 2015 +0000

        * ipa-devirt.c (odr_types_equivalent_p): Fix formating.
        (add_type_duplicate): Fix comparison of BINFOs.


    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@220546
138bc75d-0d04-0410-96
1f-82ee72b054a4

I can post a patch.


  parent reply	other threads:[~2015-03-02 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65276-4@http.gcc.gnu.org/bugzilla/>
2015-03-02 13:39 ` burnus at gcc dot gnu.org
2015-03-02 13:51 ` rguenth at gcc dot gnu.org
2015-03-02 16:31 ` aldyh at gcc dot gnu.org
2015-03-02 17:30 ` hubicka at gcc dot gnu.org
2015-03-02 17:47 ` aldyh at gcc dot gnu.org [this message]
2015-03-02 17:53 ` hubicka at ucw dot cz
2015-03-02 18:44 ` aldyh at gcc dot gnu.org
2015-03-02 18:46 ` aldyh 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-65276-4-TlJ6eVzRHO@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).