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/115262] New: [15 regression] gcc.target/powerpc/pr66144-3.c fails after r15-831-g05daf617ea22e1
Date: Tue, 28 May 2024 15:57:06 +0000 [thread overview]
Message-ID: <bug-115262-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115262
Bug ID: 115262
Summary: [15 regression] gcc.target/powerpc/pr66144-3.c fails
after r15-831-g05daf617ea22e1
Product: gcc
Version: 15.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:05daf617ea22e1d818295ed2d037456937e23530, r15-831-g05daf617ea22e1
make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr66144-3.c"
FAIL: gcc.target/powerpc/pr66144-3.c scan-assembler \\mxxsel\\M
This is probably just a test case that needs assembler instruction counts
updated.
commit 05daf617ea22e1d818295ed2d037456937e23530 (HEAD)
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Sat May 25 12:39:05 2024 -0600
[committed] [v2] More logical op simplifications in simplify-rtx.cc
next reply other threads:[~2024-05-28 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 15:57 seurer at gcc dot gnu.org [this message]
2024-05-29 7:36 ` [Bug testsuite/115262] " rguenth at gcc dot gnu.org
2024-06-10 22:39 ` law at gcc dot gnu.org
2024-06-11 20:37 ` bergner at gcc dot gnu.org
2024-06-12 2:39 ` linkw at gcc dot gnu.org
2024-06-12 19:50 ` bergner at gcc dot gnu.org
2024-06-13 2:08 ` cvs-commit at gcc dot gnu.org
2024-06-13 2:10 ` 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-115262-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).