public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "venkataramanan.kumar at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/44141] Redundant loads and stores generated for AMD bdver1 target
Date: Wed, 28 Mar 2012 10:42:00 -0000	[thread overview]
Message-ID: <bug-44141-4-uSKY60HP1L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44141-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Venkataramanan <venkataramanan.kumar at amd dot com> 2012-03-28 10:32:31 UTC ---
(In reply to comment #12)
> Having a vector mode changing subreg on the LHS of an instruction is a very
> common issue in the i386 backend, and unfortunately e.g. means that lots of
> insns can't be combined or simplified.  I wonder if the expansion sometimes
> shouldn't use a non-subregged temporary as lhs and add a move from subreg of
> the temporary to the desired destination.

The expander now converts as shown below for unaligned moves with V2DF mode.

            if (TARGET_SSE_PACKED_SINGLE_INSN_OPTIMAL)
                {
                  op0 = gen_lowpart (V4SFmode, op0);
                  op1 = gen_lowpart (V4SFmode, op1);
                  emit_insn (gen_sse_movups (op0, op1));
                  return;
                }

You mean conversion is not needed here?  


> BTW, if with TARGET_SSE_PACKED_SINGLE_INSN_OPTIMAL ps is more desirable than pd
> for movs, then perhaps it would be better to add a mode attr similar to
> ssemodesuffix, which would emit pd or ps for V2DFmode depending on
> TARGET_SSE_PACKED_SINGLE_INSN_OPTIMAL (see e.g. i128 mode attr).

Yes with TARGET_SSE_PACKED_SINGLE_INSN_OPTIMAL we want to generate movups
instead of movupd.


  parent reply	other threads:[~2012-03-28 10:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44141-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:21 ` [Bug target/44141] " xiaoyuanbo at yeah dot net
2012-03-22 13:24 ` venkataramanan.kumar at amd dot com
2012-03-22 13:26 ` venkataramanan.kumar at amd dot com
2012-03-22 13:29 ` venkataramanan.kumar at amd dot com
2012-03-22 13:56 ` ubizjak at gmail dot com
2012-03-27 10:52 ` venkataramanan.kumar at amd dot com
2012-03-27 11:27 ` venkataramanan.kumar at amd dot com
2012-03-27 17:05 ` [Bug rtl-optimization/44141] " ubizjak at gmail dot com
2012-03-28  3:23 ` venkataramanan.kumar at amd dot com
2012-03-28  7:08 ` ubizjak at gmail dot com
2012-03-28  8:01 ` jakub at gcc dot gnu.org
2012-03-28 10:42 ` venkataramanan.kumar at amd dot com [this message]
2012-03-28 10:53 ` jakub at gcc dot gnu.org
2012-04-01  7:55 ` venkataramanan.kumar at amd dot com
2012-05-07 17:28 ` uweigand at gcc dot gnu.org
2012-05-08 10:28 ` [Bug target/44141] " rguenth at gcc dot gnu.org
2012-05-08 10:36 ` ubizjak at gmail dot com
2012-05-09 17:04 ` ubizjak at gmail dot com
2012-05-09 18:37 ` uros at gcc dot gnu.org
2012-05-09 20:42 ` ubizjak at gmail dot com

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-44141-4-uSKY60HP1L@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).