From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: gcc-patches@gcc.gnu.org, schwab@linux-m68k.org, juzhe.zhong@rivai.ai
Subject: Re: [PATCH] RISC-V: Fix RVV testcases.
Date: Fri, 18 Nov 2022 13:07:24 -0700 [thread overview]
Message-ID: <4688e5af-a172-ad0d-259f-b1c3f9371e18@gmail.com> (raw)
In-Reply-To: <CA+yXCZDbVqyeerVc-ZVa1oda3M7ecpj8siyvZu6OGVTCrjpvWw@mail.gmail.com>
On 11/5/22 18:13, Kito Cheng via Gcc-patches wrote:
> Alternative fix for those testcase has posted:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605126.html
Did this ever get addressed, in either form?
jeff
prev parent reply other threads:[~2022-11-18 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 1:40 juzhe.zhong
2022-10-31 22:00 ` Jeff Law
2022-10-31 22:25 ` 钟居哲
2022-10-31 22:30 ` Palmer Dabbelt
2022-10-31 23:52 ` 钟居哲
2022-11-01 18:35 ` Palmer Dabbelt
2022-11-06 0:13 ` Kito Cheng
2022-11-18 20:07 ` 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=4688e5af-a172-ad0d-259f-b1c3f9371e18@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=schwab@linux-m68k.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).