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/101444] New: [12 regression] cc.target/powerpc/pr86731-fwrapv-longlong.c fails after r12-2266
Date: Tue, 13 Jul 2021 19:47:16 +0000 [thread overview]
Message-ID: <bug-101444-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101444
Bug ID: 101444
Summary: [12 regression]
cc.target/powerpc/pr86731-fwrapv-longlong.c fails
after r12-2266
Product: gcc
Version: 12.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:063eba7ca73030139a3bf822ed127cf09b2fc226, r12-2266
make -k check-gcc
RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr86731-fwrapv-longlong.c"
FAIL: gcc.target/powerpc/pr86731-fwrapv-longlong.c scan-assembler-times
\\mp?lxv\\M|\\mlxv\\M|\\mlxvd2x\\M 2
# of expected passes 3
# of unexpected failures 1
This opnly fails on powerpc64 LE on a power 8 system.
commit 063eba7ca73030139a3bf822ed127cf09b2fc226 (HEAD, refs/bisect/bad)
Author: Michael Meissner <meissner@linux.ibm.com>
Date: Tue Jul 13 00:36:43 2021 -0400
Deal with prefixed loads/stores in tests, PR testsuite/100166
next reply other threads:[~2021-07-13 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 19:47 seurer at gcc dot gnu.org [this message]
2021-07-14 6:11 ` [Bug testsuite/101444] " rguenth at gcc dot gnu.org
2022-05-06 8:30 ` [Bug testsuite/101444] [12/13 regression] gcc.target/powerpc/pr86731-fwrapv-longlong.c " jakub at gcc dot gnu.org
2023-05-08 12:22 ` [Bug testsuite/101444] [12/13/14 " rguenth at gcc dot gnu.org
2024-01-04 7:37 ` linkw 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-101444-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).