public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115669] [15 Regression] rv64gcv -fwrapv miscompile since r15-1006-gd93353e6423
Date: Wed, 26 Jun 2024 17:56:27 +0000 [thread overview]
Message-ID: <bug-115669-4-MZNBdHtLF8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115669-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115669
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=115450
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick O'Neill from comment #0)
> Found via fuzzer but Vineet bisected the 502.gcc_r benchmark breakage in
> spec2017 for the riscv target to the same commit so this _might_ be the same
> issue.
So the 502.gcc_r miscompile might be PR 115450 since that is for aarch64 SVE
even.
next prev parent reply other threads:[~2024-06-26 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 17:45 [Bug tree-optimization/115669] New: " patrick at rivosinc dot com
2024-06-26 17:56 ` pinskia at gcc dot gnu.org [this message]
2024-06-26 21:12 ` [Bug tree-optimization/115669] " pinskia at gcc dot gnu.org
2024-06-26 21:15 ` pinskia at gcc dot gnu.org
2024-06-27 5:56 ` [Bug tree-optimization/115669] [15 Regression] rv64gcv/aarch64+sve " rguenth at gcc dot gnu.org
2024-06-27 6:30 ` rguenth at gcc dot gnu.org
2024-06-27 8:21 ` rguenth at gcc dot gnu.org
2024-06-27 8:32 ` rguenth at gcc dot gnu.org
2024-06-27 12:11 ` cvs-commit at gcc dot gnu.org
2024-06-27 12:12 ` rguenth at gcc dot gnu.org
2024-06-27 12:24 ` [Bug tree-optimization/115669] [12/13/14 " rguenth 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-115669-4-MZNBdHtLF8@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).