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/100750] New: new test case gcc.target/powerpc/rop-5.c fails on BE
Date: Mon, 24 May 2021 22:50:24 +0000 [thread overview]
Message-ID: <bug-100750-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100750
Bug ID: 100750
Summary: new test case gcc.target/powerpc/rop-5.c fails on BE
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:5bd66c6826e5f3a38ba393702923feb88959f845, r12-814
make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/rop-5.c"
FAIL: gcc.target/powerpc/rop-5.c (test for excess errors)
# of unexpected failures 1
Fails on both power 7 and power 8 BE.
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/rop-5.c: In
function 'foo':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/rop-5.c:12:1:
error: '-mrop-protect' requires the ELFv2 ABI
(lots more instances of that message)
commit 5bd66c6826e5f3a38ba393702923feb88959f845
Author: Bill Schmidt <wschmidt@linux.ibm.com>
Date: Thu May 13 13:33:35 2021 -0500
next reply other threads:[~2021-05-24 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 22:50 seurer at gcc dot gnu.org [this message]
2021-05-26 15:49 ` [Bug testsuite/100750] " seurer at gcc dot gnu.org
2021-06-01 16:11 ` cvs-commit at gcc dot gnu.org
2021-06-01 16:19 ` wschmidt at gcc dot gnu.org
2021-06-01 20:43 ` wschmidt at gcc dot gnu.org
2021-06-01 20:47 ` cvs-commit at gcc dot gnu.org
2021-06-02 14:36 ` wschmidt at gcc dot gnu.org
2021-09-17 6:43 ` pinskia 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-100750-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).