From: Jeff Law <jeffreyalaw@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: [PATCH] RISC-V: Fix two testscases related to -std changes.
Date: Mon, 4 Dec 2023 08:20:19 -0700 [thread overview]
Message-ID: <46202110-6519-4598-a532-fad7400de308@gmail.com> (raw)
In-Reply-To: <157b3c54-d18f-4908-b20b-b6726545b999@gmail.com>
On 12/4/23 06:17, Robin Dapp wrote:
> Hi,
>
> recent -std changes caused testsuite failures. Fix those by adding
> -std=gnu99 and -Wno-incompatible-pointer-types.
>
> Going to commit as obvious.
>
> Regards
> Robin
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/autovec/pr112552.c: Add
> -Wno-incompatible-pointer-types.
> * gcc.target/riscv/rvv/autovec/struct/struct_vect_run-10.c:
> Add -std=gnu99.
THanks. Seeing light fallout from this stuff is totally expected.
My tester has churned through its supported *-elf targets and all those
have been fixed. Now it's just a matter of waiting for the native
emulated targets which only fire once a week.
Jeff
prev parent reply other threads:[~2023-12-04 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 13:17 Robin Dapp
2023-12-04 15:20 ` Jeff Law [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=46202110-6519-4598-a532-fad7400de308@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=rdapp.gcc@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).