public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28367] accessing via union on a vector does not cause vec_extract to be used
Date: Wed, 16 Mar 2011 11:58:00 -0000 [thread overview]
Message-ID: <bug-28367-4-E6dyAKht9O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28367-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28367
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-16 11:41:03 UTC ---
comment #1 is fixed, the original problem persists. optimized dump:
;; Function f (f)
f (vector(4) float t)
{
union
{
vector(4) float t1;
float t2[4];
} t5;
float D.2687;
<bb 2>:
t5.t1 = t_1(D);
D.2687_2 = t5.t2[0];
return D.2687_2;
}
FRE does not know how to handle different sizes in its support for
type-punning stores/loads (visit_reference_op_load).
Mine.
next parent reply other threads:[~2011-03-16 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28367-4@http.gcc.gnu.org/bugzilla/>
2011-03-16 11:58 ` rguenth at gcc dot gnu.org [this message]
2014-10-10 0:25 ` glisse at gcc dot gnu.org
2014-11-24 9:03 ` rguenth at gcc dot gnu.org
2006-07-13 2:43 [Bug middle-end/28367] New: " pinskia at gcc dot gnu dot org
2006-07-13 5:37 ` [Bug middle-end/28367] " pinskia at gcc dot gnu dot org
2006-07-14 7:58 ` pinskia at gcc dot gnu dot org
2006-07-19 14:46 ` pinskia at gcc dot gnu dot org
2006-08-26 4:48 ` pinskia 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=bug-28367-4-E6dyAKht9O@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).