public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55755] Invalid VIEW_CONVERT_EXPR produced by SRA
Date: Thu, 20 Dec 2012 14:28:00 -0000 [thread overview]
Message-ID: <bug-55755-4-iJ4lfBcv9n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55755-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55755
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2012-12-20
AssignedTo|unassigned at gcc dot |jamborm at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #1 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-12-20 14:28:07 UTC ---
Obviously mine. The fix for release branches is probably going to be
add !access->grp_unscalarizable_region test to most to a few
access_has_children_p tests. The proper fix is to re-work
access_has_children_p to a predicate returning true if there are any
replacements in any of its children. But let me audit the
access_has_children_p tests first.
next prev parent reply other threads:[~2012-12-20 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 14:22 [Bug tree-optimization/55755] New: " jamborm at gcc dot gnu.org
2012-12-20 14:28 ` jamborm at gcc dot gnu.org [this message]
2013-01-04 13:03 ` [Bug tree-optimization/55755] " jamborm at gcc dot gnu.org
2013-01-04 13:21 ` jamborm at gcc dot gnu.org
2013-01-24 14:54 ` jamborm at gcc dot gnu.org
2013-01-24 15:41 ` jamborm at gcc dot gnu.org
2013-01-24 15:53 ` jamborm 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-55755-4-iJ4lfBcv9n@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).