From: Jakub Jelinek <jakub@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: Marc Glisse <marc.glisse@inria.fr>,
Michael Zolotukhin <michael.v.zolotukhin@gmail.com>,
Kirill Yukhin <kirill.yukhin@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [i386] scalar ops that preserve the high part of a vector
Date: Fri, 07 Dec 2012 14:47:00 -0000 [thread overview]
Message-ID: <20121207144725.GY2315@tucnak.redhat.com> (raw)
In-Reply-To: <50C20079.8050001@redhat.com>
On Fri, Dec 07, 2012 at 08:43:05AM -0600, Richard Henderson wrote:
> > +(define_insn "<sse>_vm<plusminus_insn><mode>3<vec_merge_or_concat>"
> > [(set (match_operand:VF_128 0 "register_operand" "=x,x")
> > (vec_merge:VF_128
> > - (plusminus:VF_128
> > - (match_operand:VF_128 1 "register_operand" "0,x")
> > - (match_operand:VF_128 2 "nonimmediate_operand" "xm,xm"))
> > + (vec_duplicate:VF_128
> > + (plusminus:<ssescalarmode>
> > + (vec_select:<ssescalarmode>
> > + (match_operand:VF_128 1 "register_operand" "0,x")
> > + (parallel [(const_int 0)]))
> > + (match_operand:<ssescalarmode> 2 "nonimmediate_operand" "xm,xm")))
> > (match_dup 1)
> > (const_int 1)))]
> > "TARGET_SSE"
> > "@
> > <plusminus_mnemonic><ssescalarmodesuffix>\t{%2, %0|%0, %2}
> > v<plusminus_mnemonic><ssescalarmodesuffix>\t{%2, %1, %0|%0, %1, %2}"
> > [(set_attr "isa" "noavx,avx")
> > (set_attr "type" "sseadd")
> > (set_attr "prefix" "orig,vex")
> > (set_attr "mode" "<ssescalarmode>")])
>
> Did this really trigger as a substitution? It's not supposed to have, since
> you didn't add (set_attr "replace_vec_merge_with_vec_concat" "yes")...
That was the older proposal, the current way to trigger it is using
the substitution attr somewhere, typically in pattern name
- <vec_merge_or_concat> in the above case.
Jakub
next prev parent reply other threads:[~2012-12-07 14:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 9:33 Marc Glisse
2012-10-14 9:54 ` Uros Bizjak
2012-10-14 12:52 ` Marc Glisse
2012-11-30 12:36 ` Marc Glisse
2012-11-30 13:55 ` Uros Bizjak
2012-11-30 22:36 ` Marc Glisse
2012-12-01 17:27 ` Marc Glisse
2012-12-02 10:51 ` Uros Bizjak
2012-12-02 12:30 ` Marc Glisse
2012-12-03 8:53 ` Uros Bizjak
2012-12-03 15:34 ` Marc Glisse
2012-12-03 17:55 ` Uros Bizjak
2012-12-04 14:05 ` Marc Glisse
2012-12-04 16:28 ` Marc Glisse
2012-12-04 18:06 ` Uros Bizjak
2012-12-04 18:12 ` H.J. Lu
2012-12-06 13:42 ` Kirill Yukhin
2012-12-07 6:50 ` Michael Zolotukhin
2012-12-07 8:46 ` Uros Bizjak
2012-12-07 8:49 ` Marc Glisse
2012-12-07 10:52 ` Michael Zolotukhin
2012-12-07 14:02 ` Marc Glisse
2012-12-07 14:43 ` Richard Henderson
2012-12-07 14:47 ` Jakub Jelinek [this message]
2012-12-07 14:53 ` Richard Henderson
2012-12-07 15:00 ` Marc Glisse
2012-12-07 15:06 ` Richard Henderson
2012-12-07 15:12 ` Marc Glisse
2012-12-07 16:24 ` Richard Henderson
2012-12-07 17:23 ` Marc Glisse
2012-12-08 5:47 ` Marc Glisse
2012-12-12 15:48 ` Richard Henderson
2012-12-05 14:22 ` Marc Glisse
2012-12-05 17:07 ` Paolo Bonzini
2012-12-05 20:22 ` Marc Glisse
2012-12-05 21:05 ` Eric Botcazou
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=20121207144725.GY2315@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=kirill.yukhin@gmail.com \
--cc=marc.glisse@inria.fr \
--cc=michael.v.zolotukhin@gmail.com \
--cc=rth@redhat.com \
--cc=ubizjak@gmail.com \
/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).