From: Palmer Dabbelt <palmer@rivosinc.com>
To: pinskia@gmail.com
Cc: jeffreyalaw@gmail.com, philipp.tomsich@vrull.eu,
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: Tue, 08 Nov 2022 20:53:07 -0800 (PST) [thread overview]
Message-ID: <mhng-c51e9766-0c21-4c9b-8304-b878552eb33f@palmer-ri-x1c9a> (raw)
In-Reply-To: <CA+=Sn1mm7Vjj9LxPycQoOGGCXdxBwyFizK_akL+PNVB-6XSNew@mail.gmail.com>
On Tue, 08 Nov 2022 20:43:20 PST (-0800), pinskia@gmail.com wrote:
> On Tue, Nov 8, 2022 at 7:16 PM 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.)
>
> Using contrib/git-commit-mklog.py can help here to make sure you
> always get the correct format for the changelog and it does a decent
> job of figuring out function names too.
> You can also use contrib/gcc-git-customization.sh to install it such
> that you can use it when doing git commits.
> After invoking that inside the GCC git; you can just do "git
> gcc-commit-mklog ...." Where .... would be what you normally put for
> "git commit" (but as if in the toplevel directory).
Thanks, that's awesome.
next prev parent reply other threads:[~2022-11-09 4:53 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 [this message]
2022-11-09 9:27 ` Philipp Tomsich
2022-11-09 9:33 ` Philipp Tomsich
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=mhng-c51e9766-0c21-4c9b-8304-b878552eb33f@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--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=philipp.tomsich@vrull.eu \
--cc=pinskia@gmail.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).