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 libstdc++/98384] New: new test case 20_util/to_chars/long_double.cc in r11-6249 fails on powerpc64 BE Date: Fri, 18 Dec 2020 21:39:38 +0000 [thread overview] Message-ID: <bug-98384-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98384 Bug ID: 98384 Summary: new test case 20_util/to_chars/long_double.cc in r11-6249 fails on powerpc64 BE Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3c57e692357c79ee7623dfc1586652aee2aefb8f, r11-6249 make -k check RUNTESTFLAGS="conformance.exp=20_util/to_chars/long_double.cc" FAIL: 20_util/to_chars/long_double.cc (test for excess errors) # of unexpected failures 1 # of unresolved testcases 1 commit 3c57e692357c79ee7623dfc1586652aee2aefb8f Author: Patrick Palka <ppalka@redhat.com> Date: Thu Dec 17 23:11:34 2020 -0500 libstdc++: Add floating-point std::to_chars implementation This new test case is failing on powerpc64 big endian machines. It works fine on LE machines. /home/seurer/gcc/git/build/gcc-test/./gcc/xg++ -shared-libgcc -B/home/seurer/gcc/git/build/gcc-test/./gcc -nostdinc++ -L/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/src -L/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/src/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs -B/home/seurer/gcc/git/install/gcc-test/powerpc64-unknown-linux-gnu/bin/ -B/home/seurer/gcc/git/install/gcc-test/powerpc64-unknown-linux-gnu/lib/ -isystem /home/seurer/gcc/git/install/gcc-test/powerpc64-unknown-linux-gnu/include -isystem /home/seurer/gcc/git/install/gcc-test/powerpc64-unknown-linux-gnu/sys-include -B/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs -fmessage-length=0 -fno-show-column -ffunction-sections -fdata-sections -g -O2 -D_GNU_SOURCE -DLOCALEDIR="." -nostdinc++ -I/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu -I/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include -I/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++ -I/home/seurer/gcc/git/gcc-test/libstdc++-v3/include/backward -I/home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/util /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc -include bits/stdc++.h -fdiagnostics-plain-output ./libtestc++.a -Wl,--gc-sections -L/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/src/filesystem/.libs -lm -o ./long_double.exe /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc: In function 'void test01()': /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:42: error: 'nextdownl' was not declared in this scope; did you mean 'nexttowardl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:43: error: 'nextupl' was not declared in this scope; did you mean 'expl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc: In function 'void test02()': /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:175: error: 'nextdownl' was not declared in this scope; did you mean 'nexttowardl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:184: error: 'nextupl' was not declared in this scope; did you mean 'expl'? compiler exited with status 1 FAIL: 20_util/to_chars/long_double.cc (test for excess errors) Excess errors: /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:42: error: 'nextdownl' was not declared in this scope; did you mean 'nexttowardl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:43: error: 'nextupl' was not declared in this scope; did you mean 'expl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:175: error: 'nextdownl' was not declared in this scope; did you mean 'nexttowardl'? /home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/20_util/to_chars/long_double.cc:184: error: 'nextupl' was not declared in this scope; did you mean 'expl'?
next reply other threads:[~2020-12-18 21:39 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-18 21:39 seurer at gcc dot gnu.org [this message] 2020-12-21 20:28 ` [Bug libstdc++/98384] " ppalka at gcc dot gnu.org 2020-12-22 9:23 ` ro at gcc dot gnu.org 2021-01-05 9:10 ` [Bug libstdc++/98384] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-07 13:04 ` iains at gcc dot gnu.org 2021-01-07 15:42 ` ppalka at gcc dot gnu.org 2021-01-07 16:41 ` iains at gcc dot gnu.org 2021-01-07 17:42 ` cvs-commit at gcc dot gnu.org 2021-01-07 17:55 ` ppalka at gcc dot gnu.org 2021-01-08 9:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-01-12 16:35 ` ppalka at gcc dot gnu.org 2021-01-14 11:13 ` rguenth at gcc dot gnu.org 2021-02-12 15:02 ` jakub at gcc dot gnu.org 2021-02-23 2:49 ` cvs-commit at gcc dot gnu.org 2021-02-23 16:55 ` ppalka at gcc dot gnu.org 2021-02-24 9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-02-24 15:14 ` ppalka at gcc dot gnu.org 2021-02-24 15:42 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-02-24 15:48 ` jakub at gcc dot gnu.org 2021-02-24 16:16 ` ppalka at gcc dot gnu.org 2021-02-24 16:26 ` iains at gcc dot gnu.org 2021-02-24 16:45 ` ppalka at gcc dot gnu.org 2021-02-24 17:26 ` cvs-commit at gcc dot gnu.org 2021-02-27 16:17 ` iains at gcc dot gnu.org 2021-02-27 16:49 ` dje at gcc dot gnu.org 2021-03-03 14:28 ` ppalka at gcc dot gnu.org 2021-03-05 2:37 ` dje at gcc dot gnu.org 2021-03-08 17:42 ` ppalka at gcc dot gnu.org 2021-03-08 17:53 ` schwab@linux-m68k.org 2021-03-08 19:27 ` dje at gcc dot gnu.org 2021-03-08 21:09 ` iains at gcc dot gnu.org 2021-03-08 21:24 ` iains at gcc dot gnu.org 2021-03-09 9:55 ` iains at gcc dot gnu.org 2021-03-10 14:28 ` ppalka at gcc dot gnu.org 2021-03-10 14:51 ` ppalka at gcc dot gnu.org 2021-04-08 15:11 ` cvs-commit at gcc dot gnu.org 2021-04-08 15:22 ` [Bug libstdc++/98384] new test case 20_util/to_chars/long_double.cc in r11-6249 fails ppalka at gcc dot gnu.org 2021-04-08 16:22 ` redi at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` jakub 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-98384-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: linkBe 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).