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 testsuite/114518] New: [14 regression] gcc.target/powerpc/combine-2-2.c fails after r14-9692-g839bc42772ba7a Date: Thu, 28 Mar 2024 14:03:48 +0000 [thread overview] Message-ID: <bug-114518-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114518 Bug ID: 114518 Summary: [14 regression] gcc.target/powerpc/combine-2-2.c fails after r14-9692-g839bc42772ba7a Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:839bc42772ba7af66af3bd16efed4a69511312ae, r14-9692-g839bc42772ba7a Seeing this on BE only. make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32,-m64}' powerpc.exp=gcc.target/powerpc/combine-2-2.c" FAIL: gcc.target/powerpc/combine-2-2.c scan-assembler-not \\msrawi\\M commit 839bc42772ba7af66af3bd16efed4a69511312ae (HEAD) Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Wed Mar 27 14:09:52 2024 +0000 combine: Don't combine if I2 does not change
next reply other threads:[~2024-03-28 14:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 14:03 seurer at gcc dot gnu.org [this message] 2024-03-28 23:09 ` [Bug testsuite/114518] " segher at gcc dot gnu.org 2024-03-29 0:58 ` seurer at gcc dot gnu.org 2024-03-29 13:16 ` segher at gcc dot gnu.org 2024-04-02 8:23 ` rguenth at gcc dot gnu.org 2024-04-10 6:01 ` [Bug testsuite/114518] [15 " rguenth at gcc dot gnu.org 2024-04-16 1:00 ` bergner 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-114518-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).