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 target/53101] Recognize casts to sub-vectors
Date: Tue, 24 Apr 2012 11:14:00 -0000	[thread overview]
Message-ID: <bug-53101-4-KnLKcSu5ne@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53101-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-04-24
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-24 11:13:33 UTC ---
We get MEM[(T * {ref-all})&x] for the casting (not a BIT_FIELD_REF for
example).
This gets expanded to

(insn 6 5 7 (set (reg:OI 63)
        (subreg:OI (reg/v:V4DF 61 [ x ]) 0)) t.c:8 -1
     (nil))

(insn 7 6 8 (set (reg:V2DF 60 [ <retval> ])
        (subreg:V2DF (reg:OI 63) 0)) t.c:8 -1
     (nil))

but that should be perfectly optimizable.


  reply	other threads:[~2012-04-24 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 10:18 [Bug target/53101] New: " marc.glisse at normalesup dot org
2012-04-24 11:14 ` rguenth at gcc dot gnu.org [this message]
2012-05-01 15:10 ` [Bug target/53101] " marc.glisse at normalesup dot org
2012-05-01 17:18 ` marc.glisse at normalesup dot org
2012-05-03 19:20 ` marc.glisse at normalesup dot org
2012-05-06 20:31 ` glisse at gcc dot gnu.org
2012-11-11 22:18 ` glisse at gcc dot gnu.org
2012-11-16 23:04 ` glisse at gcc dot gnu.org
2021-08-19 19:49 ` pinskia 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-53101-4-KnLKcSu5ne@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).