From: Edwin Lu <ewlu@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com
Subject: Re: [Committed] RISC-V: Add Types to Un-Typed Risc-v Instructions:
Date: Tue, 5 Sep 2023 10:13:07 -0700 [thread overview]
Message-ID: <92e22e69-0af6-4426-8364-2b6f3912be9e@rivosinc.com> (raw)
In-Reply-To: <69cea6d5-8b87-aba2-fbee-8940e6097201@gmail.com>
On 9/1/2023 11:02 AM, Jeff Law wrote:
>
>
> On 8/31/23 11:32, Edwin Lu wrote:
>> Related Discussion:
>> https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5eb2@gmail.com/
>>
>>
>> This patch updates the riscv instructions to ensure that no insn is left
>> without a type attribute. Added new types: "trap" (self explanatory)
>> and "cbo"
>> (for cache related instructions)
>>
>> Tested for regressions using rv32/64 multilib for linux/newlib. Also
>> tested
>> rv32/64 gcv for linux.
>>
>> gcc/Changelog:
>>
>> * config/riscv/riscv.md: Update/Add types
> OK.
>
> jeff
Committed!
Edwin
prev parent reply other threads:[~2023-09-05 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 17:32 [PATCH] " Edwin Lu
2023-09-01 18:02 ` Jeff Law
2023-09-05 17:13 ` Edwin Lu [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=92e22e69-0af6-4426-8364-2b6f3912be9e@rivosinc.com \
--to=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.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).