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 libffi/109447] New: test case libffi.closures/cls_align_longdouble_split.c fails
Date: Fri, 07 Apr 2023 17:48:00 +0000 [thread overview]
Message-ID: <bug-109447-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109447
Bug ID: 109447
Summary: test case libffi.closures/cls_align_longdouble_split.c
fails
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libffi
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
When running make check on libffi there are two failures. Note that this only
occurs on systems where the compiler was built with
--with-long-double-format=ieee. I see these on both gcc 12 and trunk. I don't
know yet if it is a regression but I am checking.
On powerpc the libffi library is built and tested if go is included in the
languages.
FAIL: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O0
output pattern test
FAIL: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O2
output pattern test
=== libffi Summary ===
# of expected passes 1460
# of unexpected failures 2
# of unsupported tests 28
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/./gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/./gcc/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/bin/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/lib/
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/sys-include
/home/seurer/gcc/git/gcc-test/libffi/testsuite/libffi.closures/cls_align_longdouble_split.c
-W -Wall -Wno-psabi -O0 -mlong-double-128
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/include
-I/home/seurer/gcc/git/gcc-test/libffi/testsuite/../include
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/include/..
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs
-lffi -lm -o ./cls_align_longdouble_split.exe^M
PASS: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O0
(test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs:.:/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs:
Execution timeout is: 300
spawn [open ...]^M
1 1 1 1 1 1 1 8 8 8 8 8 8 9: 9 9 9 9 9 9 10
res: 9 9 9 9 9 9 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21
res: 9 11 13 15 17 19 21
PASS: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O0
execution test
FAIL: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O0
output pattern test
Output was:
1 1 1 1 1 1 1 8 8 8 8 8 8 9: 9 9 9 9 9 9 10
res: 9 9 9 9 9 9 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21
res: 9 11 13 15 17 19 21
Should match:
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21^M?
res: 9 11 13 15 17 19 21^M?
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21^M?
res: 9 11 13 15 17 19 21
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/./gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/./gcc/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/bin/
-B/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/lib/
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/include
-isystem
/home/seurer/gcc/git/install/gcc-test/powerpc64le-unknown-linux-gnu/sys-include
/home/seurer/gcc/git/gcc-test/libffi/testsuite/libffi.closures/cls_align_longdouble_split.c
-W -Wall -Wno-psabi -O2 -mlong-double-128
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/include
-I/home/seurer/gcc/git/gcc-test/libffi/testsuite/../include
-I/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/include/..
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs
-L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs
-lffi -lm -o ./cls_align_longdouble_split.exe^M
PASS: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O2
(test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs:.:/home/seurer/gcc/git/build/gcc-test/gcc:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libffi/.libs:/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libstdc++-v3/src/.libs:
Execution timeout is: 300
spawn [open ...]^M
1 1 1 1 1 1 1 8 8 8 8 8 8 9: 9 9 9 9 9 9 10
res: 9 9 9 9 9 9 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21
res: 9 11 13 15 17 19 21
PASS: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O2
execution test
FAIL: libffi.closures/cls_align_longdouble_split.c -W -Wall -Wno-psabi -O2
output pattern test
Output was:
1 1 1 1 1 1 1 8 8 8 8 8 8 9: 9 9 9 9 9 9 10
res: 9 9 9 9 9 9 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21
res: 9 11 13 15 17 19 21
Should match:
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21^M?
res: 9 11 13 15 17 19 21^M?
1 2 3 4 5 6 7 8 9 10 11 12 13 14: 9 11 13 15 17 19 21^M?
res: 9 11 13 15 17 19 21
next reply other threads:[~2023-04-07 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 17:48 seurer at gcc dot gnu.org [this message]
2023-04-07 18:53 ` [Bug libffi/109447] " schwab@linux-m68k.org
2023-04-08 3:21 ` bergner at gcc dot gnu.org
2023-04-08 3:36 ` bergner at gcc dot gnu.org
2023-04-08 15:37 ` bergner at gcc dot gnu.org
2023-04-08 15:37 ` bergner at gcc dot gnu.org
2023-04-08 16:14 ` segher at gcc dot gnu.org
2023-04-08 18:00 ` bergner at gcc dot gnu.org
2023-05-06 15:31 ` cvs-commit at gcc dot gnu.org
2023-05-06 20:59 ` cvs-commit at gcc dot gnu.org
2023-05-09 19:58 ` 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-109447-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).