From: "Roger Sayle" <roger@nextmovesoftware.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [x86 PATCH] Correct ix86_rtx_cost for multi-word multiplication.
Date: Tue, 17 May 2022 17:44:20 +0100 [thread overview]
Message-ID: <00b701d86a0d$5c648400$152d8c00$@nextmovesoftware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
This is the i386 backend specific piece of my revised patch for
PR middle-end/98865, where Richard Biener has suggested that I perform
the desired transformation during RTL expansion where the backend can
control whether it is profitable to convert a multiplication into a
bit-wise AND and a negation. This works well for x86_64, but alas
exposes a latent bug with -m32, where a DImode multiplication incorrectly
appears to be cheaper than negdi2+anddi3(!?). The fix to ix86_rtx_costs
is to report that a DImode (multi-word) multiplication actually requires
three SImode multiplications and two SImode additions. This also corrects
the cost of TImode multiplication on TARGET_64BIT.
This patch has been tested on x86_64-pc-linux-gnu with make bootstrap
and make -k check, both with and without --target_board=unix{-m32}, with
no new failures. This change avoids the need for a !ia32 target selector
for the upcoming new test case gcc.target/i386/pr98865.c.
Ok for mainline?
2022-05-17 Roger Sayle <roger@nextmovesoftware.com>
gcc/ChangeLog
* config/i386/i386.cc (ix86_rtx_costs) [MULT]: When mode size
is wider than word_mode, a multiplication costs three word_mode
multiplications and two word_mode additions.
Thanks in advance,
Roger
--
[-- Attachment #2: patchmc0.txt --]
[-- Type: text/plain, Size: 874 bytes --]
diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc
index 86752a6..e8a2229 100644
--- a/gcc/config/i386/i386.cc
+++ b/gcc/config/i386/i386.cc
@@ -20634,7 +20634,17 @@ ix86_rtx_costs (rtx x, machine_mode mode, int outer_code_i, int opno,
op0 = XEXP (op0, 0), mode = GET_MODE (op0);
}
- *total = (cost->mult_init[MODE_INDEX (mode)]
+ int mult_init;
+ // Double word multiplication requires 3 mults and 2 adds.
+ if (GET_MODE_SIZE (mode) > UNITS_PER_WORD)
+ {
+ mult_init = 3 * cost->mult_init[MODE_INDEX (word_mode)]
+ + 2 * cost->add;
+ nbits *= 3;
+ }
+ else mult_init = cost->mult_init[MODE_INDEX (mode)];
+
+ *total = (mult_init
+ nbits * cost->mult_bit
+ rtx_cost (op0, mode, outer_code, opno, speed)
+ rtx_cost (op1, mode, outer_code, opno, speed));
next reply other threads:[~2022-05-17 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:44 Roger Sayle [this message]
2022-05-18 9:21 ` Uros Bizjak
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='00b701d86a0d$5c648400$152d8c00$@nextmovesoftware.com' \
--to=roger@nextmovesoftware.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).