From: Jeff Law <jeffreyalaw@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>,
Demin Han <demin.han@starfivetech.com>,
Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Fix uninitialized and redundant use of which_alternative
Date: Fri, 28 Jul 2023 15:55:16 -0600 [thread overview]
Message-ID: <38e8217c-fcbf-7d7f-d7e5-e45fd89965e5@gmail.com> (raw)
In-Reply-To: <b78ec2b0-9632-0249-bc9e-ec22f5e64ad0@rivosinc.com>
On 7/28/23 10:42, Patrick O'Neill wrote:
> No worries! I'm glad it was an easy fix ;)
Note there's an effort underway via RISE to have some official RISC-V
continuous testing for the compiler tools in place in the very near
future (before Sept 1).
We're starting with a limited POC, so my thinking is to use it to
augment what's already running in my tester.
Specifically I'm looking to add rv64gc and rv32gc cross testing for both
the coordination branch and the trunk. No multilibs in the immediate
future, but once it's up and running and we have a good sense of the
monthly cost we can look to add key multilibs such as vector or Zb*.
The hope is we can catch and resolve these minor problems quickly.
Jeff
next prev parent reply other threads:[~2023-07-28 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 9:48 demin.han
2023-07-27 10:22 ` juzhe.zhong
2023-07-27 11:57 ` Kito Cheng
2023-07-27 20:46 ` Patrick O'Neill
2023-07-28 2:55 ` Demin Han
2023-07-28 16:42 ` Patrick O'Neill
2023-07-28 21:55 ` Jeff Law [this message]
[not found] ` <9819777D4BE5D5B8+4EB8A5B1-0546-4283-910B-CD4EA60B1F7A@rivai.ai>
2023-07-28 16:37 ` [Committed] RISC-V: Specify -mabi in rv64 autovec testcase Patrick O'Neill
2023-07-28 16:40 ` [PATCH] RISC-V: Fix uninitialized and redundant use of which_alternative Patrick O'Neill
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=38e8217c-fcbf-7d7f-d7e5-e45fd89965e5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=demin.han@starfivetech.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=patrick@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).