From: Palmer Dabbelt <palmer@rivosinc.com>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: kito.cheng@sifive.com, juzhe.zhong@rivai.ai, pinskia@gmail.com,
gcc-patches@gcc.gnu.org, Patrick O'Neill <patrick@rivosinc.com>
Subject: Re: RISC-V Test Errors and Failures
Date: Tue, 16 May 2023 19:47:12 -0700 (PDT) [thread overview]
Message-ID: <mhng-31725886-abc6-4efa-8b85-368d5c1e4d4a@palmer-ri-x1c9a> (raw)
In-Reply-To: <d9508028-cdf2-196e-cee5-0f23465afbc7@rivosinc.com>
On Tue, 16 May 2023 19:46:28 PDT (-0700), Vineet Gupta wrote:
> On 5/16/23 19:21, Kito Cheng wrote:
>> Palmer:
>>
>> For short-term, this should help your internal test:
>> https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1233
>
> That only helps if using bleeding edge toolchain scripts (which I
> regularly do and so did Patrick).
>
> Palmer has a fork of toolchain scripts and I'm assuming he hasn't caught
> up to that point ;-)
I'm fine dropping the fork if the bugs have been fixed. IIRC last week
we were still waiting for them to merge something?
> -Vineet
next prev parent reply other threads:[~2023-05-17 2:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 1:57 juzhe.zhong
2023-05-17 2:02 ` Andrew Pinski
2023-05-17 2:07 ` juzhe.zhong
2023-05-17 2:13 ` Palmer Dabbelt
2023-05-17 2:20 ` Kito Cheng
2023-05-17 2:21 ` Kito Cheng
2023-05-17 2:46 ` Vineet Gupta
2023-05-17 2:47 ` Palmer Dabbelt [this message]
2023-05-17 2:51 ` Patrick O'Neill
2023-05-17 2:53 ` Palmer Dabbelt
2023-05-17 3:08 ` Vineet Gupta
2023-05-17 3:11 ` Palmer Dabbelt
2023-05-17 3:33 ` Kito Cheng
2023-05-17 4:04 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 23:06 Palmer Dabbelt
2023-05-17 0:16 ` Vineet Gupta
2023-05-17 0:20 ` Palmer Dabbelt
2023-05-17 1:04 ` Vineet Gupta
2023-05-17 1:29 ` Palmer Dabbelt
2023-05-17 2:00 ` Jeff Law
2023-05-17 2:05 ` Palmer Dabbelt
2023-05-17 2:32 ` Jeff Law
2023-05-17 2:39 ` Palmer Dabbelt
2023-05-17 4:08 ` Jeff Law
2023-05-17 2:08 ` Vineet Gupta
2023-05-17 2:12 ` Jeff Law
2023-05-17 7:52 ` Andreas Schwab
2023-05-19 0:13 ` Vineet Gupta
2023-05-25 20:29 ` Thomas Schwinge
2023-05-26 0:04 ` Vineet Gupta
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-31725886-abc6-4efa-8b85-368d5c1e4d4a@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=patrick@rivosinc.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).