public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106838] Built-in traits have wrong preconditions
Date: Tue, 06 Sep 2022 10:29:44 +0000 [thread overview]
Message-ID: <bug-106838-4-S3jM3Tyfgs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106838-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106838
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> All traits of kind C currently reject T[] and T[1], but should accept them.
Gah, they do in gcc-12, but not trunk, sorry.
But they do reject incomplete unions, which should be accepted.
And traits of kind A incorrectly allow Incomplete[1].
And traits of kind B incorrectly allow Incomplete[].
Here's a testcase:
struct I;
// A.
// "T shall be a complete type, (possibly cv-qualified) void,"
// "or an array of unknown bound."
void kindA()
{
// No incomplete object types.
(void) __is_constructible(I); // { dg-error "incomplete type" "FAILS" }
(void) __is_constructible(I[1]); // { dg-error "incomplete type" "FAILS" }
// Except arrays of unknown bound.
(void) __is_constructible(I[]);
}
// B.
// "remove_all_extents_t<T> shall be a complete type or cv void."
void kindB()
{
// No incomplete types, including arrays.
(void) __is_trivial(I); // { dg-error "incomplete type" }
(void) __is_trivial(I[1]); // { dg-error "incomplete type" }
(void) __is_trivial(I[]); // { dg-error "incomplete type" "FAILS" }
}
union U;
// C.
// "If T is a non-union class type, T shall be a complete type."
void kindC()
{
// No incomplete non-union class types.
(void) __is_empty(I); // { dg-error "incomplete type" }
// But arrays of incomplete type are OK.
(void) __is_empty(I[1]); // { dg-bogus "incomplete type" "FAILS" }
(void) __is_empty(I[]);
// And incomplete unions are OK.
(void) __is_empty(U); // { dg-bogus "incomplete type" "FAILS" }
(void) __is_empty(U[1]); // { dg-bogus "incomplete type" "FAILS" }
(void) __is_empty(U[]);
}
The dg-error lines marked FAIL are incorrectly accepted. The dg-bogus lines are
incorrectly rejected.
next prev parent reply other threads:[~2022-09-06 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 17:06 [Bug c++/106838] New: " redi at gcc dot gnu.org
2022-09-05 17:06 ` [Bug c++/106838] " redi at gcc dot gnu.org
2022-09-05 17:32 ` redi at gcc dot gnu.org
2022-09-05 21:16 ` redi at gcc dot gnu.org
2022-09-05 21:21 ` redi at gcc dot gnu.org
2022-09-06 10:29 ` redi at gcc dot gnu.org [this message]
2022-09-06 10:32 ` redi at gcc dot gnu.org
2022-09-06 12:28 ` redi at gcc dot gnu.org
2022-09-06 12:28 ` redi at gcc dot gnu.org
2022-09-08 18:32 ` cvs-commit at gcc dot gnu.org
2022-09-08 18:32 ` redi 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-106838-4-S3jM3Tyfgs@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).