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 target/108699] New: gcc.c-torture/execute/builtin-bitops-1.c fails on power 9 BE
Date: Tue, 07 Feb 2023 15:01:13 +0000 [thread overview]
Message-ID: <bug-108699-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699
Bug ID: 108699
Summary: gcc.c-torture/execute/builtin-bitops-1.c fails on
power 9 BE
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
This fails for 32 bits powerpc64 BE on a power 9 (only) and it fails for trunk
and gcc 12, 11, and 10.
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
execute.exp=gcc.c-torture/execute/builtin-bitops-1.c"
FAIL: gcc.c-torture/execute/builtin-bitops-1.c -Os execution test
# of expected passes 15
# of unexpected failures 1
spawn -ignore SIGHUP
^M
PASS: gcc.c-torture/execute/builtin-bitops-1.c -Os (test for excess errors)
Setting LD_LIBRARY_PATH to
:/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/gcc/32::/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/gcc/32:/home/seurer/gcc/git/build/gcc-test/./gmp/.libs:/home/seurer/gcc/git/build/gcc-test/./prev-gmp/.libs:/home/seurer/gcc/git/build/gcc-test/./mpfr/src/.libs:/home/seurer/gcc/git/build/gcc-test/./prev-mpfr/src/.libs:/home/seurer/gcc/git/build/gcc-test/./mpc/src/.libs:/home/seurer/gcc/git/build/gcc-test/./prev-mpc/src/.libs:/home/seurer/gcc/git/build/gcc-test/./isl/.libs:/home/seurer/gcc/git/build/gcc-test/./prev-isl/.libs
Execution timeout is: 300
spawn [open ...]^M
FAIL: gcc.c-torture/execute/builtin-bitops-1.c -Os execution test
(gdb) run
Starting program: /home/seurer/gcc/git/build/gcc-test/builtin-bitops-1.exe
Program received signal SIGABRT, Aborted.
0x0fd737a0 in ?? () from /lib32/libc.so.6
(gdb) where
#0 0x0fd737a0 in ?? () from /lib32/libc.so.6
#1 0x0fd15424 in raise () from /lib32/libc.so.6
#2 0x0fcfa428 in abort () from /lib32/libc.so.6
#3 0x10000408 in main () at
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.c-torture/execute/builtin-bitops-1.c:182
There are a bunch of aborts in this test but the reported line # must be off.
next reply other threads:[~2023-02-07 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 15:01 seurer at gcc dot gnu.org [this message]
2023-02-14 12:12 ` [Bug target/108699] " linkw at gcc dot gnu.org
2023-02-14 17:39 ` segher at gcc dot gnu.org
2023-02-15 2:34 ` linkw at gcc dot gnu.org
2023-04-04 5:13 ` cvs-commit at gcc dot gnu.org
2023-04-17 9:06 ` cvs-commit at gcc dot gnu.org
2023-04-17 9:08 ` cvs-commit at gcc dot gnu.org
2023-04-17 9:09 ` cvs-commit at gcc dot gnu.org
2023-06-02 4:15 ` bergner at gcc dot gnu.org
2023-06-02 4:42 ` 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-108699-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).