public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/111688] [14 regression] bootstrap failure after r14-4382-g1be18ea110a2d6 Date: Thu, 05 Oct 2023 12:10:45 +0000 [thread overview] Message-ID: <bug-111688-4-USjFHwyuwy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111688 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:1f7295af6029b6497e9928fe279fd166b94ce2c2 commit r14-4413-g1f7295af6029b6497e9928fe279fd166b94ce2c2 Author: Martin Jambor <mjambor@suse.cz> Date: Thu Oct 5 14:08:47 2023 +0200 Revert "ipa: Self-DCE of uses of removed call LHSs (PR 108007)" This reverts commit 1be18ea110a2d69570dbc494588a7c73173883be. As reported in PR bootstrap/111688, it broke ppc64le bootstrap because of a debug-compare failure.
next prev parent reply other threads:[~2023-10-05 12:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-04 2:27 [Bug bootstrap/111688] New: [14 regression] bootstrap failure after r14-4383-g14d0c509898b03 seurer at gcc dot gnu.org 2023-10-04 9:57 ` [Bug bootstrap/111688] " rguenth at gcc dot gnu.org 2023-10-04 13:28 ` jamborm at gcc dot gnu.org 2023-10-04 13:45 ` jamborm at gcc dot gnu.org 2023-10-04 13:54 ` seurer at gcc dot gnu.org 2023-10-04 15:23 ` jamborm at gcc dot gnu.org 2023-10-04 17:20 ` jamborm at gcc dot gnu.org 2023-10-05 9:43 ` [Bug bootstrap/111688] [14 regression] bootstrap failure after r14-4382-g1be18ea110a2d6 jamborm at gcc dot gnu.org 2023-10-05 12:10 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-05 12:12 ` jamborm 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-111688-4-USjFHwyuwy@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: linkBe 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).