public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114200] [14] RISC-V fixed-length vector miscompile at -O3
Date: Thu, 07 Mar 2024 00:31:21 +0000 [thread overview]
Message-ID: <bug-114200-4-hv7PILVVsn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114200-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114200
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Patrick O'Neill <patrick at rivosinc dot com> ---
Thanks for the fix!
Once the other ICEs (pr114196, pr114195) get resolved I'll be able to turn on
the yarpgen fuzzer without getting overwhelmed with duplicates.
The failures from the existing csmith fuzzer are getting more rare :)
next prev parent reply other threads:[~2024-03-07 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 1:15 [Bug target/114200] New: " patrick at rivosinc dot com
2024-03-06 12:55 ` [Bug target/114200] " rdapp at gcc dot gnu.org
2024-03-06 19:42 ` cvs-commit at gcc dot gnu.org
2024-03-06 19:43 ` rdapp at gcc dot gnu.org
2024-03-07 0:31 ` patrick at rivosinc dot com [this message]
2024-03-07 5:39 ` pinskia at gcc dot gnu.org
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=bug-114200-4-hv7PILVVsn@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).