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 other/107665] New: [13 regression] g++.dg/cpp23/ext-floating1.C fails after r13-3387-g79d38dd46e6b07
Date: Sun, 13 Nov 2022 05:00:34 +0000 [thread overview]
Message-ID: <bug-107665-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107665
Bug ID: 107665
Summary: [13 regression] g++.dg/cpp23/ext-floating1.C fails
after r13-3387-g79d38dd46e6b07
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
Tried g:79d38dd46e6b07e5a90ab25df1438eb0918eb475, r13-3387-g79d38dd46e6b07
make -k check-gcc RUNTESTFLAGS="dg.exp=g++.dg/cpp23/ext-floating1.C"
FAIL: g++.dg/cpp23/ext-floating1.C -std=gnu++23 (test for excess errors)
# of unexpected failures 1
This is failing on powerpc64 when the compiler is built with
--with-long-double-format=ieee.
Excess errors:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/cpp23/ext-floating1.C:27:54:
error: static assertion failed
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/cpp23/ext-floating1.C:28:54:
error: static assertion failed
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/cpp23/ext-floating1.C:29:61:
error: static assertion failed
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/cpp23/ext-floating1.C:30:61:
error: static assertion failed
The failures are here:
#ifdef __SIZEOF_FLOAT128__
static_assert (is_same<decltype (0.0q), __float128>::value);
static_assert (is_same<decltype (0.0Q), __float128>::value);
static_assert (is_same<decltype (0.0q + 0.0q), __float128>::value);
static_assert (is_same<decltype (0.0Q + 0.0Q), __float128>::value);
#endif
commit 79d38dd46e6b07e5a90ab25df1438eb0918eb475 (HEAD)
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Oct 19 18:55:46 2022 +0200
testsuite: Default make check-g++ vs. tests for newest C++ standard
next reply other threads:[~2022-11-13 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 5:00 seurer at gcc dot gnu.org [this message]
2022-11-13 7:47 ` [Bug other/107665] " pinskia at gcc dot gnu.org
2022-11-15 14:27 ` [Bug target/107665] " 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-107665-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).