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 middle-end/64922] [5 Regression] runtime error: member call on misaligned address for type 'struct _Rep' Date: Wed, 04 Feb 2015 21:55:00 -0000 [thread overview] Message-ID: <bug-64922-4-gV6EiJfo14@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64922-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64922 --- Comment #12 from Jan Hubicka <hubicka at gcc dot gnu.org> --- OK, the devirtualization I see is for _Z3getI10Code_BlockEbR2CSRKSsPT_.part.3.constprop.7 when it is inlined to _ZN4FileC2ERKSs outer type of original context is: $6 = {offset = 0, speculative_offset = 0, outer_type = 0x7ffff631f498, speculative_outer_type = 0x0, maybe_in_construction = 0, maybe_derived_type = 1, where outer_type is Code_Block. It gets combined with: $10 = {offset = 0, speculative_offset = 0, outer_type = 0x7ffff6cb0000, speculative_outer_type = 0x0, maybe_in_construction = 0, maybe_derived_type = 0, speculative_maybe_derived_type = 0, invalid = 0, dynamic = 1} where outer_type is basic_string These two types are not related, so we go for invalid. The first type is derived from fact that operator >> takes reference to Code_Block that seems OK. The other is determined by std::basic_string<char>::basic_string (&D.13149, "X", &D.13150); that is passed to _62 = get<Code_Block> (_30, &D.13149, _36); So I think we confuse argument 2 of get<Code_Block> with argument 1 of get<Code_Block>.part.3.
next prev parent reply other threads:[~2015-02-04 21:55 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-03 16:19 [Bug middle-end/64922] New: " mpolacek at gcc dot gnu.org 2015-02-03 16:21 ` [Bug middle-end/64922] " mpolacek at gcc dot gnu.org 2015-02-03 16:23 ` mpolacek at gcc dot gnu.org 2015-02-03 16:59 ` jakub at gcc dot gnu.org 2015-02-03 20:04 ` jakub at gcc dot gnu.org 2015-02-04 17:53 ` [Bug middle-end/64922] [5 Regression] " hubicka at gcc dot gnu.org 2015-02-04 18:39 ` hubicka at gcc dot gnu.org 2015-02-04 18:43 ` jakub at gcc dot gnu.org 2015-02-04 20:06 ` jakub at gcc dot gnu.org 2015-02-04 20:09 ` jakub at gcc dot gnu.org 2015-02-04 20:10 ` jakub at gcc dot gnu.org 2015-02-04 20:29 ` hubicka at gcc dot gnu.org 2015-02-04 21:55 ` hubicka at gcc dot gnu.org [this message] 2015-02-04 22:00 ` hubicka at gcc dot gnu.org 2015-02-04 23:00 ` hubicka at gcc dot gnu.org 2015-02-05 10:10 ` jakub 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-64922-4-gV6EiJfo14@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).