public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: jeffreyalaw@gmail.com, gcc-patches@gcc.gnu.org,
	 Kito Cheng <kito.cheng@gmail.com>,
	christoph.muellner@vrull.eu,  Vineet Gupta <vineetg@rivosinc.com>,
	jlaw@ventanamicro.com
Subject: Re: [PATCH] RISC-V: costs: handle BSWAP
Date: Wed, 9 Nov 2022 10:33:55 +0100	[thread overview]
Message-ID: <CAAeLtUC-=qFsp6dNQeF82Ud8e-pY0vRaZ3WbrdznwVEcPHrttg@mail.gmail.com> (raw)
In-Reply-To: <mhng-0d6fcebe-163f-4571-9009-ae4e2a41d796@palmer-ri-x1c9a>

Applied to master, with the commit-message regenerated as:

    gcc/ChangeLog:

            * config/riscv/riscv.cc (riscv_rtx_costs): Add BSWAP.

Thanks,
Philipp.

On Wed, 9 Nov 2022 at 04:15, Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> On Tue, 08 Nov 2022 18:57:26 PST (-0800), jeffreyalaw@gmail.com wrote:
> >
> > On 11/8/22 12:54, Philipp Tomsich wrote:
> >> The BSWAP operation is not handled in rtx_costs. Add it.
> >>
> >> With Zbb, BSWAP for XLEN is a single instruction; for smaller modes,
> >> it will expand into two.
> >>
> >> gcc/ChangeLog:
> >>
> >>          * config/riscv/riscv.c (rtx_costs): Add BSWAP.
> >
> > OK.
>
> It's riscv_rtx_costs.
>
> (I don't usually read ChangeLog entries that closely, just happened to
> stumble on it when poking around.)
>
>
> >
> > Jeff

      parent reply	other threads:[~2022-11-09  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:54 Philipp Tomsich
2022-11-09  2:57 ` Jeff Law
2022-11-09  3:15   ` Palmer Dabbelt
2022-11-09  4:43     ` Andrew Pinski
2022-11-09  4:53       ` Palmer Dabbelt
2022-11-09  9:27       ` Philipp Tomsich
2022-11-09  9:33     ` Philipp Tomsich [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='CAAeLtUC-=qFsp6dNQeF82Ud8e-pY0vRaZ3WbrdznwVEcPHrttg@mail.gmail.com' \
    --to=philipp.tomsich@vrull.eu \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jlaw@ventanamicro.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=vineetg@rivosinc.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).