From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: Kito Cheng <kito.cheng@sifive.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: Use stdint-gcc.h in rvv testsuite
Date: Tue, 7 Nov 2023 11:47:43 +0100 [thread overview]
Message-ID: <CAEg0e7g-qhHMaLJXC6x_==84Kjo2YNAfMYw3LBHB887z9Ok2bA@mail.gmail.com> (raw)
In-Reply-To: <CALLt3Tj902=afWB3y9Vm+WKcJdKasJVytRCFyQeuv-w89KxD=g@mail.gmail.com>
On Tue, Nov 7, 2023 at 11:16 AM Kito Cheng <kito.cheng@sifive.com> wrote:
>
> LGTM, but title is little bit misleading, it's not really related to rvv, change to either RISC-V or T-head is fine, anyway, you can commit without send v2 :)
Fixed and pushed.
Thanks!
>
> Christoph Muellner <christoph.muellner@vrull.eu> 於 2023年11月7日 週二 17:45 寫道:
>>
>> From: Christoph Müllner <christoph.muellner@vrull.eu>
>>
>> stdint.h can be replaced with stdint-gcc.h to resolve some missing
>> system headers in non-multilib installations.
>>
>> gcc/testsuite/ChangeLog:
>>
>> * gcc.target/riscv/xtheadmemidx-helpers.h:
>> Replace stdint.h with stdint-gcc.h.
>>
>> Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
>> ---
>> gcc/testsuite/gcc.target/riscv/xtheadmemidx-helpers.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gcc/testsuite/gcc.target/riscv/xtheadmemidx-helpers.h b/gcc/testsuite/gcc.target/riscv/xtheadmemidx-helpers.h
>> index a97f08c5cc1..9d8ce124a93 100644
>> --- a/gcc/testsuite/gcc.target/riscv/xtheadmemidx-helpers.h
>> +++ b/gcc/testsuite/gcc.target/riscv/xtheadmemidx-helpers.h
>> @@ -1,7 +1,7 @@
>> #ifndef XTHEADMEMIDX_HELPERS_H
>> #define XTHEADMEMIDX_HELPERS_H
>>
>> -#include <stdint.h>
>> +#include <stdint-gcc.h>
>>
>> #define intX_t long
>> #define uintX_t unsigned long
>> --
>> 2.41.0
>>
next prev parent reply other threads:[~2023-11-07 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 9:45 Christoph Muellner
2023-11-07 10:16 ` Kito Cheng
2023-11-07 10:47 ` Christoph Müllner [this message]
2023-11-07 17:41 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2023-09-26 17:58 Patrick O'Neill
2023-09-26 18:13 ` Andrew Pinski
2023-09-26 18:30 ` Patrick O'Neill
2023-10-02 13:57 ` Kito Cheng
2023-10-03 20:58 ` Patrick O'Neill
2023-10-05 22:43 ` Jeff Law
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='CAEg0e7g-qhHMaLJXC6x_==84Kjo2YNAfMYw3LBHB887z9Ok2bA@mail.gmail.com' \
--to=christoph.muellner@vrull.eu \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
/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).