From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH, i386]: Fix xop_vmfrcz<mode>2 expander
Date: Thu, 13 Feb 2014 16:49:00 -0000 [thread overview]
Message-ID: <CAFULd4YjrO3jQgfy2qzFnjj+9VJ+VL0_TA6miM5ku8npgQVwBQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
Hello!
No functional changes.
2014-02-13 Uros Bizjak <ubizjak@gmail.com>
* config/i386/sse.md (xop_vmfrcz<mode>2): Generate const0 in
operands[2], not operands[3].
Tested on x86_64-pc-linux-gnu {,-m32} and committed to mainline SVN.
Uros.
[-- Attachment #2: p.diff.txt --]
[-- Type: text/plain, Size: 549 bytes --]
Index: config/i386/sse.md
===================================================================
--- config/i386/sse.md (revision 207762)
+++ config/i386/sse.md (working copy)
@@ -13618,10 +13618,10 @@
(unspec:VF_128
[(match_operand:VF_128 1 "nonimmediate_operand")]
UNSPEC_FRCZ)
- (match_dup 3)
+ (match_dup 2)
(const_int 1)))]
"TARGET_XOP"
- "operands[3] = CONST0_RTX (<MODE>mode);")
+ "operands[2] = CONST0_RTX (<MODE>mode);")
(define_insn "*xop_vmfrcz<mode>2"
[(set (match_operand:VF_128 0 "register_operand" "=x")
reply other threads:[~2014-02-13 16:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFULd4YjrO3jQgfy2qzFnjj+9VJ+VL0_TA6miM5ku8npgQVwBQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@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).