public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/111688] New: [14 regression] bootstrap failure after r14-4383-g14d0c509898b03 Date: Wed, 04 Oct 2023 02:27:09 +0000 [thread overview] Message-ID: <bug-111688-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111688 Bug ID: 111688 Summary: [14 regression] bootstrap failure after r14-4383-g14d0c509898b03 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:14d0c509898b0361f78284c05556035edde6d1e0, r14-4383-g14d0c509898b03 make . . . Comparing stages 2 and 3 Bootstrap comparison failure! powerpc64le-unknown-linux-gnu/libstdc++-v3/src/.libs/compatibility-ldbl.o differs powerpc64le-unknown-linux-gnu/libstdc++-v3/src/compatibility-ldbl.o differs commit 14d0c509898b0361f78284c05556035edde6d1e0 (HEAD) Author: Martin Jambor <mjambor@suse.cz> Date: Tue Oct 3 18:44:52 2023 +0200 ipa-sra: Allow IPA-SRA in presence of returns which will be removed
next reply other threads:[~2023-10-04 2:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-04 2:27 seurer at gcc dot gnu.org [this message] 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 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@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).