From: Palmer Dabbelt <palmer@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Clean up the pr106602.c testcase
Date: Mon, 17 Apr 2023 12:19:52 -0700 (PDT) [thread overview]
Message-ID: <mhng-16ef7009-a227-429e-9787-b62c31fa9e91@palmer-ri-x1c9a> (raw)
In-Reply-To: <cff09a47-27f0-c5e2-0c07-f5b3c4852121@gmail.com>
On Tue, 11 Apr 2023 14:01:06 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
>
>
> On 4/11/23 13:03, Palmer Dabbelt wrote:
>> The test case that was added is rv64i-specific, as there's better ways
>> to generate this code on rv32i (where the long/int cast is a NOP) and on
>> rv64i_zba (where we have word shifts). This renames the original test
>> case and adds two more for those targets.
>>
>> gcc/testsuite/ChangeLog:
>> PR target/106602
>> * gcc.target/riscv/pr106602.c: Moved to...
>> * gcc.target/riscv/pr106602-rv64i.c: ...here.
>> * gcc.target/riscv/pr106602-rv32i.c: New test.
>> * gcc.target/riscv/pr106602-rv64i_zba.c: New test.
>> ---
>> The test suite is still running, but it looks like it's made it past
>> these so I figured I'd send it now as otherwise I might forget.
>>
>> OK for trunk? (assuming the tests finish and pass)
> OK
Committed.
prev parent reply other threads:[~2023-04-17 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 19:03 Palmer Dabbelt
2023-04-11 21:01 ` Jeff Law
2023-04-17 19:19 ` Palmer Dabbelt [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=mhng-16ef7009-a227-429e-9787-b62c31fa9e91@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
/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).