public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/111601] [14 Regression] bootstrap fails in stagestrain in libcody on x86_64-linux-gnu and powerpc64le-linux-gnu
Date: Thu, 19 Oct 2023 06:23:46 +0000 [thread overview]
Message-ID: <bug-111601-4-NSl6rntNBP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111601
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
I'd say we probably miscompile cp/call.cc:tourney - you could try marking that
noinline (or verify whether it has been inlined). There's some wrong-code
bugs related to the loop header copying changes (also profile related) and
also loop-splitting.
I suspect bisecting will end up in a related area.
Most helpful would really be to bisect this.
next prev parent reply other threads:[~2023-10-19 6:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:27 [Bug bootstrap/111601] New: " doko at gcc dot gnu.org
2023-09-26 17:15 ` [Bug bootstrap/111601] " pinskia at gcc dot gnu.org
2023-10-17 2:11 ` bergner at gcc dot gnu.org
2023-10-18 13:31 ` doko at gcc dot gnu.org
2023-10-18 19:48 ` bergner at gcc dot gnu.org
2023-10-18 20:41 ` bergner at gcc dot gnu.org
2023-10-18 20:53 ` pinskia at gcc dot gnu.org
2023-10-18 21:26 ` bergner at gcc dot gnu.org
2023-10-19 6:23 ` rguenth at gcc dot gnu.org [this message]
2023-11-17 5:33 ` jeevitha at gcc dot gnu.org
2023-11-24 19:59 ` jakub at gcc dot gnu.org
2023-11-26 21:36 ` [Bug bootstrap/111601] [14 Regression] profilebootstrap " jakub at gcc dot gnu.org
2023-11-27 11:37 ` jakub at gcc dot gnu.org
2023-11-27 12:24 ` rguenther at suse dot de
2023-11-27 12:27 ` jakub at gcc dot gnu.org
2023-11-27 13:31 ` jakub at gcc dot gnu.org
2023-11-27 13:51 ` jakub at gcc dot gnu.org
2023-11-27 15:14 ` jakub at gcc dot gnu.org
2023-11-27 16:21 ` jakub at gcc dot gnu.org
2023-11-27 16:45 ` jakub at gcc dot gnu.org
2023-11-27 16:57 ` jakub at gcc dot gnu.org
2023-11-27 17:01 ` jakub at gcc dot gnu.org
2023-11-27 18:33 ` jakub at gcc dot gnu.org
2023-11-27 19:24 ` jakub at gcc dot gnu.org
2023-11-27 20:02 ` jakub at gcc dot gnu.org
2023-11-27 20:17 ` jakub at gcc dot gnu.org
2023-11-29 8:18 ` cvs-commit at gcc dot gnu.org
2023-11-29 8:31 ` jakub at gcc dot gnu.org
2023-11-30 17:20 ` jeevitha 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-111601-4-NSl6rntNBP@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).