From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH, i386]: Do not limit the cost of moves to/from XMM register to minimum 8.
Date: Thu, 29 Aug 2019 20:01:00 -0000 [thread overview]
Message-ID: <CAFULd4ZOgSxG5sn2Y7Rbpn8mcykO29mV_LenpKK+KuAte-0m_g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
2019-08-28 Uroš Bizjak <ubizjak@gmail.com>
* config/i386/i386.c (ix86_register_move_cost): Do not
limit the cost of moves to/from XMM register to minimum 8.
Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
Actually committed as r274994 with the wrong ChangeLog.
Uros.
[-- Attachment #2: q.diff.txt --]
[-- Type: text/plain, Size: 762 bytes --]
diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index 49ab50ea41bf..11c75be113e0 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -18601,9 +18601,9 @@ ix86_register_move_cost (machine_mode mode, reg_class_t class1_i,
where integer modes in SSE registers are not tieable
because of missing QImode and HImode moves to, from or between
MMX/SSE registers. */
- return MAX (8, SSE_CLASS_P (class1)
- ? ix86_cost->hard_register.sse_to_integer
- : ix86_cost->hard_register.integer_to_sse);
+ return (SSE_CLASS_P (class1)
+ ? ix86_cost->hard_register.sse_to_integer
+ : ix86_cost->hard_register.integer_to_sse);
if (MAYBE_FLOAT_CLASS_P (class1))
return ix86_cost->hard_register.fp_move;
next reply other threads:[~2019-08-29 18:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:01 Uros Bizjak [this message]
2019-08-30 7:12 ` Hongtao Liu
2019-08-30 7:16 ` Hongtao Liu
2019-08-30 7:22 ` Uros Bizjak
2019-08-30 7:30 ` Hongtao Liu
-- strict thread matches above, loose matches on Subject: below --
2019-08-28 16:12 [PATCH, i386]: Improve STV conversion of shifts Uros Bizjak
2019-08-29 8:49 ` Uros Bizjak
2019-08-30 7:40 ` Richard Biener
2019-08-30 8:29 ` [PATCH, i386]: Do not limit the cost of moves to/from XMM register to minimum 8 Uros Bizjak
2019-08-31 3:01 ` Alan Modra
2019-08-31 16:12 ` Richard Biener
2019-09-01 19:49 ` Uros Bizjak
2019-09-02 7:16 ` Alan Modra
2019-09-02 8:13 ` Hongtao Liu
2019-09-02 8:41 ` Uros Bizjak
2019-09-03 7:57 ` Hongtao Liu
2019-09-03 11:24 ` Richard Biener
2019-09-03 11:33 ` Richard Biener
2019-09-03 16:50 ` Uros Bizjak
2019-09-04 1:42 ` Hongtao Liu
2019-09-05 5:47 ` Hongtao Liu
2019-09-05 8:54 ` Uros Bizjak
2019-09-02 10:23 ` Richard Biener
2019-09-03 1:37 ` Hongtao Liu
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=CAFULd4ZOgSxG5sn2Y7Rbpn8mcykO29mV_LenpKK+KuAte-0m_g@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).