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/99233] New: [11 regression] new test case gcc.target/powerpc/pr96264.c in r11-7285 fails
Date: Wed, 24 Feb 2021 00:41:48 +0000 [thread overview]
Message-ID: <bug-99233-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99233
Bug ID: 99233
Summary: [11 regression] new test case
gcc.target/powerpc/pr96264.c in r11-7285 fails
Product: gcc
Version: 11.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:d1efec57e279f5b0cd62073696cd351fce369bb7, r11-7285
make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr96264.c"
FAIL: gcc.target/powerpc/pr96264.c execution test
# of expected passes 1
# of unexpected failures 1
Is this an endian problem? It fails on BE but works on LE.
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr96264.c
-fdiagnostics-plain-output -Os -fno-forward-propagate -fschedule-insns
-fno-tree-ter -Wno-psabi -lm -o ./pr96264.exe
PASS: gcc.target/powerpc/pr96264.c (test for excess errors)
Execution timeout is: 300
spawn [open ...]
FAIL: gcc.target/powerpc/pr96264.c execution test
=== gcc Summary ===
# of expected passes 1
# of unexpected failures 1
(gdb) run
Starting program: /home/seurer/gcc/git/build/gcc-test/./pr96264.exe
Program received signal SIGABRT, Aborted.
0x00003fffb7cd268c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) where
#0 0x00003fffb7cd268c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1 0x00003fffb7cd4878 in __GI_abort () at abort.c:90
#2 0x0000000010000590 in .main ()
next reply other threads:[~2021-02-24 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 0:41 seurer at gcc dot gnu.org [this message]
2021-02-24 8:32 ` [Bug testsuite/99233] " rguenth at gcc dot gnu.org
2021-02-25 16:24 ` cvs-commit at gcc dot gnu.org
2021-02-26 12:59 ` rguenth at gcc dot gnu.org
2021-03-31 16:53 ` cvs-commit 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-99233-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).