public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/63226] New: ICE with -flto-odr-type-merging
Date: Thu, 11 Sep 2014 13:48:00 -0000	[thread overview]
Message-ID: <bug-63226-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63226
           Summary: ICE with -flto-odr-type-merging
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: hubicka at gcc dot gnu.org

The ICE depends on Honza's no-yet committed patch:
https://gcc.gnu.org/ml/gcc-patches/2014-09/msg00878.html

With that patch (and hence -flto-odr-type-merging), one gets the following ICE:

$ g++ -c -flto one12.ii two10.ii
$ g++ -flto -flto-odr-type-merging one12.o two10.ii


lto1: internal compiler error: in odr_types_equivalent_p, at ipa-devirt.c:1066
0x815714 odr_types_equivalent_p
        ../../gcc/ipa-devirt.c:1066
0x815a3e add_type_duplicate
        ../../gcc/ipa-devirt.c:1116


Note: -Wodr doesn't warn for this test case.


With the files one12.ii:
----------------------------------------
class ONE;
class OneClass {
  ONE *swpmi;
  OneClass ();
};
typedef struct ynodetype_t *ynode;
typedef struct ynodetype_t {
  union {
    struct { ynode child1, child3; } i;
  } y;
} ynodetype;
class ONE {
  union _xynode { ynode yn; } ;
};
OneClass::OneClass () { }
----------------------------------------

two10.ii:
----------------------------------------
class ONE;
class TwoClass {
  ONE *swpci;
  TwoClass ();
};
typedef struct ynodetype_t *ynode;
typedef struct { } yleaftype;
typedef struct ynodetype_t {
  union {
    struct { yleaftype leaf; } i;
  } y;
} ynodetype;
typedef ynode ytree;
class ONE {
  ytree Tree;
};
TwoClass::TwoClass () { }
----------------------------------------


             reply	other threads:[~2014-09-11 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 13:48 burnus at gcc dot gnu.org [this message]
2014-09-11 19:01 ` [Bug lto/63226] " hubicka at gcc dot gnu.org
2014-09-11 20:13 ` hubicka at gcc dot gnu.org
2014-09-12  0:18 ` hubicka at ucw dot cz
2014-09-12 14:55 ` burnus at gcc dot gnu.org
2014-09-12 14:55 ` burnus at gcc dot gnu.org
2014-09-12 15:02 ` burnus at gcc dot gnu.org
2014-09-15 15:03 ` [Bug lto/63226] [5 Regression] " trippels at gcc dot gnu.org
2014-09-19 21:40 ` hubicka at gcc dot gnu.org
2014-09-22 11:58 ` trippels at gcc dot gnu.org
2014-09-24 21:39 ` burnus 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-63226-4@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).