From: Edwin Lu <ewlu@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: Patrick O'Neill <patrick@rivosinc.com>
Subject: Re: [Committed V2] RISC-V: Fix regression (GCC-14 compare with GCC-13.2) of SHA256 from coremark-pro
Date: Tue, 16 Jan 2024 17:45:19 -0800 [thread overview]
Message-ID: <25972cad-10d2-47e6-ac1b-c5e558362cae@rivosinc.com> (raw)
Message-ID: <20240117014519.Tjm9WOa1gCFB8_TDF-t3EI6w9ZG_MMoqm6rYqlPYh0k@z> (raw)
In-Reply-To: <66BCDE186C6D0518+202401170941579529951@rivai.ai>
On 1/16/2024 5:41 PM, juzhe.zhong@rivai.ai wrote:
> Are you saying using glibc lib ? I do the testing with newlib, I didn't
> anything wrong.
>
Yes, I'm seeing the problem using glibc. Looking at our postcommit ci
reports, it appears to only affect linux rv32gcv.
> It seems that this patch triggers latent bug of VSETVL PASS (Even though
> this patch doesn't change anything related to VSETVL PASS).
>
> I will investigate it.
>
> Thanks.
>
Thanks!
Edwin
next prev parent reply other threads:[~2024-01-17 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 12:00 Juzhe-Zhong
2024-01-17 1:37 ` Edwin Lu
2024-01-17 1:37 ` Edwin Lu
2024-01-17 1:41 ` juzhe.zhong
2024-01-17 1:45 ` Edwin Lu [this message]
2024-01-17 1:45 ` Edwin Lu
2024-01-17 1:50 ` Li, Pan2
2024-01-26 7:53 ` juzhe.zhong
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=25972cad-10d2-47e6-ac1b-c5e558362cae@rivosinc.com \
--to=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--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).