From: Edwin Lu <ewlu@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, gnu-toolchain@rivosinc.com
Subject: Re: [PATCH 4/5][Committed] RISC-V: Update Types for RISC-V Instructions
Date: Mon, 11 Sep 2023 10:48:39 -0700 [thread overview]
Message-ID: <2125f584-920f-459f-a64f-1149967a9280@rivosinc.com> (raw)
Message-ID: <20230911174839.WeymZ8Jbd5O8YIg_cAg973htREcRI3RhVNFuTpedwIA@z> (raw)
In-Reply-To: <CA+yXCZCtgtH775eXoHHNL7a_dWQxK1e54uT2uoNggMB8cTT5rw@mail.gmail.com>
On 9/6/2023 4:23 PM, Kito Cheng via Gcc-patches wrote:
> LGTM
>
> Edwin Lu <ewlu@rivosinc.com> 於 2023年9月7日 週四 01:52 寫道:
>
>> This patch adds types to riscv instructions that were added or were
>> missed by the original patch
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628996.html
>>
>> gcc/ChangeLog:
>>
>> * config/riscv/riscv.md: Update types
>>
>> Signed-off-by: Edwin Lu <ewlu@rivosinc.com>
>> ---
>> gcc/config/riscv/riscv.md | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md
>> index c329f55db43..c1cecd27815 100644
>> --- a/gcc/config/riscv/riscv.md
>> +++ b/gcc/config/riscv/riscv.md
>> @@ -2223,6 +2223,7 @@ (define_insn "movsidf2_low_rv32"
>> "TARGET_HARD_FLOAT && !TARGET_64BIT && TARGET_ZFA"
>> "fmv.x.w\t%0,%1"
>> [(set_attr "move_type" "fmove")
>> + (set_attr "type" "fmove")
>> (set_attr "mode" "DF")])
>>
>>
>> @@ -2235,6 +2236,7 @@ (define_insn "movsidf2_high_rv32"
>> "TARGET_HARD_FLOAT && !TARGET_64BIT && TARGET_ZFA"
>> "fmvh.x.d\t%0,%1"
>> [(set_attr "move_type" "fmove")
>> + (set_attr "type" "fmove")
>> (set_attr "mode" "DF")])
>>
>> (define_insn "movdfsisi3_rv32"
>> @@ -2247,6 +2249,7 @@ (define_insn "movdfsisi3_rv32"
>> "TARGET_HARD_FLOAT && !TARGET_64BIT && TARGET_ZFA"
>> "fmvp.d.x\t%0,%2,%1"
>> [(set_attr "move_type" "fmove")
>> + (set_attr "type" "fmove")
>> (set_attr "mode" "DF")])
>>
>> (define_split
>> --
>> 2.34.1
>>
>>
>
Committed!
Edwin
next prev parent reply other threads:[~2023-09-11 17:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 17:50 [PATCH 0/5] RISC-V: Add Types to Untyped Instructions Edwin Lu
2023-09-06 17:50 ` [PATCH 1/5] RISC-V: Update Types for Vector Instructions Edwin Lu
2023-09-06 23:23 ` Kito Cheng
2023-09-07 17:26 ` Edwin Lu
2023-09-06 17:50 ` [PATCH 2/5] RISC-V: Add Types for Un-Typed zc Instructions Edwin Lu
2023-09-06 23:33 ` Kito Cheng
2023-09-07 17:29 ` Edwin Lu
2023-09-06 17:50 ` [PATCH 3/5] RISC-V: Add Types to Un-Typed Zicond Instructions Edwin Lu
2023-09-06 23:22 ` Kito Cheng
2023-09-07 0:42 ` Tsukasa OI
2023-09-07 13:17 ` Jeff Law
2023-09-11 17:48 ` [PATCH 3/5][Committed] " Edwin Lu
2023-09-11 17:48 ` Edwin Lu
2023-09-06 17:50 ` [PATCH 4/5] RISC-V: Update Types for RISC-V Instructions Edwin Lu
2023-09-06 23:23 ` Kito Cheng
2023-09-11 17:48 ` Edwin Lu [this message]
2023-09-11 17:48 ` [PATCH 4/5][Committed] " Edwin Lu
2023-09-06 17:50 ` [PATCH 5/5] RISC-V: Remove Assert Protecting Types Edwin Lu
2023-09-07 13:19 ` Jeff Law
2023-09-07 17:31 ` Edwin Lu
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=2125f584-920f-459f-a64f-1149967a9280@rivosinc.com \
--to=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@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).