public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: liuhongt <hongtao.liu@intel.com>
Cc: gcc-patches@gcc.gnu.org, crazylht@gmail.com, hjl.tools@gmail.com
Subject: Re: [PATCH] Adjust memory_move_cost for MASK_REGS when MODE_SIZE > 8.
Date: Fri, 31 Mar 2023 07:57:02 +0200	[thread overview]
Message-ID: <CAFULd4bvZoL3e=Mw9BRgnb4kBO7gjzx9jUwcBtMTCCPFzsgMRA@mail.gmail.com> (raw)
In-Reply-To: <20230331051129.2691249-1-hongtao.liu@intel.com>

On Fri, Mar 31, 2023 at 7:11 AM liuhongt <hongtao.liu@intel.com> wrote:
>
> RA sometimes will use lowest the cost of the mode with all different regclasses
> w/o check if it's hard_regno_mode_ok.
> It's impossible to put modes whose size > 8 into MASK_REGS, ajdust the cost to
> avoid potential performance issue.

I was going to ask to open a PR in order to fix RA instead of the
proposed workaround, but the patch just prevents a theoretical issue
and follows the established practice with other regclasses. Perhaps
these workarounds are not needed with the current RA, but this is a
tangential issue which should be fixed for all regclasses.

> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
> Ok for trunk?

OK.

Thanks,
Uros.

>
> gcc/ChangeLog:
>
>         * config/i386/i386.cc (inline_memory_move_cost): Return 100
>         for MASK_REGS when MODE_SIZE > 8.
> ---
>  gcc/config/i386/i386.cc | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc
> index 2cc8e9548a9..2581b800a06 100644
> --- a/gcc/config/i386/i386.cc
> +++ b/gcc/config/i386/i386.cc
> @@ -19847,9 +19847,12 @@ inline_memory_move_cost (machine_mode mode, enum reg_class regclass, int in)
>           index = 1;
>           break;
>         /* DImode loads and stores assumed to cost the same as SImode.  */
> -       default:
> +       case 4:
> +       case 8:
>           index = 2;
>           break;
> +       default:
> +         return 100;
>         }
>
>        if (in == 2)
> --
> 2.39.1.388.g2fc9e9ca3c
>

  reply	other threads:[~2023-03-31  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  5:11 liuhongt
2023-03-31  5:57 ` Uros Bizjak [this message]
2023-03-31  6:14   ` 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='CAFULd4bvZoL3e=Mw9BRgnb4kBO7gjzx9jUwcBtMTCCPFzsgMRA@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hongtao.liu@intel.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).