public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Make the default rtx_costs of MULT/DIV variants consistent.
Date: Mon, 30 May 2022 08:49:09 -0600	[thread overview]
Message-ID: <1336a156-913a-6deb-4749-755b94819164@gmail.com> (raw)
In-Reply-To: <003901d8742b$a7715db0$f6541910$@nextmovesoftware.com>



On 5/30/2022 7:46 AM, Roger Sayle wrote:
> GCC's middle-end provides a default cost model for RTL expressions, for
> backends that don't specify their own instruction timings, that can be
> summarized as multiplications are COSTS_N_INSNS(4), divisions are
> COSTS_N_INSNS(7) and all other operations are COSTS_N_INSNS(1).
> This patch tweaks the above definition so that fused-multiply-add
> (FMA) and high-part multiplications cost the same as regular
> multiplications,
> or more importantly aren't (by default) considered less expensive.  Likewise
> the saturating forms of multiplication and division cost the same as the
> regular variants.  These values can always be changed by the target, but
> the goal is to avoid RTL expansion substituting a suitable operation with
> its saturating equivalent because it (accidentally) looks much cheaper.
> For example, PR 89845 is about implementing division/modulus via highpart
> multiply, which may accidentally look extremely cheap.
>
> I believe there should be no code generation changes for this patch,
> but of course I'm happy to address any adverse changes on rare targets.
> 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.  Ok for mainline?
>
>
> 2022-05-30  Roger Sayle  <roger@nextmovesoftware.com>
>
> gcc/ChangeLog
>          * rtlanal.cc (rtx_cost) <MULT>: Treat FMA, SS_MULT, US_MULT,
>          SMUL_HIGHPART and UMUL_HIGHPART as having the same cost as MULT.
>          <DIV>: Likewise, SS_DIV and US_DIV have the same default as DIV.
OK.

Jeff

      reply	other threads:[~2022-05-30 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 13:46 Roger Sayle
2022-05-30 14:49 ` Jeff Law [this message]

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=1336a156-913a-6deb-4749-755b94819164@gmail.com \
    --to=jeffreyalaw@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).