public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112572] New: [14 regression] LLVM miscompiled since r14-5355-g3cd3a09b3f91a1
Date: Thu, 16 Nov 2023 20:06:22 +0000 [thread overview]
Message-ID: <bug-112572-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572
Bug ID: 112572
Summary: [14 regression] LLVM miscompiled since
r14-5355-g3cd3a09b3f91a1
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, rsandifo at gcc dot gnu.org,
slyfox at gcc dot gnu.org
Target Milestone: ---
LLVM's test suite has many failures for me with trunk.
CCing jakub because he was able to run with the test failure in PR109462 and
I've got a very poor track record with being able to reduce LLVM, ditto slyfox
as he has a great track record with reducing LLVM (PR110228, PR110726,
PR110598).
This bisects to the same commit as PR112568 does (r14-5355-g3cd3a09b3f91a1).
I'll add some (large) reproduction instructions in a minute.
next reply other threads:[~2023-11-16 20:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 20:06 sjames at gcc dot gnu.org [this message]
2023-11-17 0:00 ` [Bug middle-end/112572] " sjames at gcc dot gnu.org
2023-11-17 0:41 ` sjames at gcc dot gnu.org
2023-11-17 4:13 ` sjames at gcc dot gnu.org
2023-11-17 4:14 ` sjames at gcc dot gnu.org
2023-11-17 5:21 ` sjames at gcc dot gnu.org
2023-11-17 5:23 ` pinskia at gcc dot gnu.org
2023-11-17 5:28 ` pinskia at gcc dot gnu.org
2023-11-17 10:43 ` jakub at gcc dot gnu.org
2023-11-18 10:18 ` sjames at gcc dot gnu.org
2023-11-18 10:19 ` sjames at gcc dot gnu.org
2023-11-18 10:23 ` sjames at gcc dot gnu.org
2023-11-18 10:58 ` sjames at gcc dot gnu.org
2023-11-18 10:59 ` sjames at gcc dot gnu.org
2023-11-18 11:00 ` sjames at gcc dot gnu.org
2023-11-18 11:11 ` jakub at gcc dot gnu.org
2023-11-18 11:36 ` sjames at gcc dot gnu.org
2023-11-18 21:00 ` pinskia at gcc dot gnu.org
2023-11-18 21:13 ` pinskia at gcc dot gnu.org
2023-11-18 21:28 ` pinskia at gcc dot gnu.org
2023-11-18 21:38 ` slyfox at gcc dot gnu.org
2023-11-18 21:55 ` pinskia at gcc dot gnu.org
2023-11-18 22:22 ` pinskia at gcc dot gnu.org
2023-11-18 22:39 ` pinskia at gcc dot gnu.org
2023-11-18 23:06 ` rsandifo at gcc dot gnu.org
2023-11-18 23:39 ` pinskia at gcc dot gnu.org
2023-11-19 7:21 ` pinskia at gcc dot gnu.org
2023-11-19 9:24 ` ebotcazou at gcc dot gnu.org
2023-11-19 9:42 ` sjames at gcc dot gnu.org
2023-11-30 21:09 ` jakub at gcc dot gnu.org
2023-11-30 21:12 ` pinskia at gcc dot gnu.org
2023-11-30 22:29 ` sjames at gcc dot gnu.org
2023-12-04 2:49 ` pinskia at gcc dot gnu.org
2023-12-04 11:01 ` sjames at gcc dot gnu.org
2023-12-06 9:02 ` jakub at gcc dot gnu.org
2023-12-06 18:32 ` 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-112572-4@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).