From: Patrick O'Neill <patrick@rivosinc.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc-patches@gcc.gnu.org, jeffreyalaw@gmail.com,
juzhe.zhong@rivai.ai, macro@embecosm.com, vineetg@rivosinc.com,
gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] RISC-V: Use stdint-gcc.h in rvv testsuite
Date: Tue, 26 Sep 2023 11:30:47 -0700 [thread overview]
Message-ID: <b1c30bc1-5dcd-b315-f583-86dc5b857597@rivosinc.com> (raw)
In-Reply-To: <CA+=Sn1=vWL7hyL6mx7o7w0L+VXQWRVZ1J-mnvWO=YjWVvEDS=Q@mail.gmail.com>
On 9/26/23 11:13, Andrew Pinski wrote:
> On Tue, Sep 26, 2023 at 10:59 AM Patrick O'Neill <patrick@rivosinc.com> wrote:
>> stdint.h can be replaced with stdint-gcc.h to resolve some missing
>> system headers in non-multilib installations.
>>
>> Tested using glibc rv32gcv and rv64gcv on r14-4258-gc9837443075.
>>
>> gcc/ChangeLog:
>>
>> * config/riscv/riscv_vector.h (__RISCV_VECTOR_H): Replace
>> stdint.h with stdint-gcc.h
> I don't think this will work when testing an installed compiler which I do.
>
> Thanks,
> Andrew
In the riscv target testsuite (gcc.target/riscv) all occurrences of
#include <stdint.h> are currently constrained to the rvv/ subdirectory.
All non-vector tests use #include <stdint-gcc.h> rather than
#include <stdint.h>. Have you encountered any issues when testing
installations with non-vector tests?
Thanks,
Patrick
next prev parent reply other threads:[~2023-09-26 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 17:58 Patrick O'Neill
2023-09-26 18:13 ` Andrew Pinski
2023-09-26 18:30 ` Patrick O'Neill [this message]
2023-10-02 13:57 ` Kito Cheng
2023-10-03 20:58 ` Patrick O'Neill
2023-10-05 22:43 ` Jeff Law
2023-11-07 9:45 Christoph Muellner
2023-11-07 10:16 ` Kito Cheng
2023-11-07 10:47 ` Christoph Müllner
2023-11-07 17:41 ` Palmer Dabbelt
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=b1c30bc1-5dcd-b315-f583-86dc5b857597@rivosinc.com \
--to=patrick@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=macro@embecosm.com \
--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).