public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35144] [4.3 regression] ICE in generate_element_copy
Date: Sat, 09 Feb 2008 10:31:00 -0000	[thread overview]
Message-ID: <20080209103047.27345.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35144-87@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jakub at gcc dot gnu dot org  2008-02-09 10:30 -------
Why do the structs need to be the same?  They have TYPE_STRUCTURAL_EQUALITY_P
set and useless_type_conversion_p is true for these two types.  And that's the
tree-ssa check for type compatibility.  It is very likely --combine can create
similar IL, so SRA needs to be able to deal with it.
I believe we could in cp_genericize_r replace all TYPE_PTRMEMFUNC_P types
with a single canonical RECORD_TYPE representing pointer to member, I don't
think
the middle-end should care about the differences, but that would be only a
workaround for the tree-sra inability to handle structuraly equal but not
identical aggregates.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35144


  parent reply	other threads:[~2008-02-09 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 23:06 [Bug tree-optimization/35144] New: " jakub at gcc dot gnu dot org
2008-02-08 23:06 ` [Bug tree-optimization/35144] " jakub at gcc dot gnu dot org
2008-02-09  3:55 ` [Bug c++/35144] " pinskia at gcc dot gnu dot org
2008-02-09 10:31 ` jakub at gcc dot gnu dot org [this message]
2008-02-10 23:14 ` rguenth at gcc dot gnu dot org
2008-02-12 13:28 ` jakub at gcc dot gnu dot org
2008-02-12 18:36 ` jakub at gcc dot gnu dot org
2008-02-12 18:39 ` jakub at gcc dot gnu dot 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=20080209103047.27345.qmail@sourceware.org \
    --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).