public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109277] [13 Regression] type_traits:1417:30: error: invalid use of incomplete type ‘class v8::internal::WasmArray’
Date: Thu, 13 Apr 2023 18:59:48 +0000 [thread overview]
Message-ID: <bug-109277-4-uxWWhS0eVl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109277-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109277
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:f32f7881fb0db085479525b5a23db5dabd990c3b
commit r13-7172-gf32f7881fb0db085479525b5a23db5dabd990c3b
Author: Jason Merrill <jason@redhat.com>
Date: Mon Apr 3 23:20:13 2023 -0400
c++: make trait of incomplete type a permerror [PR109277]
An incomplete type argument to several traits is specified to be undefined
behavior in the library; since it's a compile-time property, we diagnose
it. But apparently some code was relying on the previous behavior of not
diagnosing. So let's make it a permerror.
The assert in cxx_incomplete_type_diagnostic didn't like that, and I don't
see the point of having the assert, so let's just remove it.
PR c++/109277
gcc/cp/ChangeLog:
* semantics.cc (check_trait_type): Handle incomplete type directly.
* typeck2.cc (cxx_incomplete_type_diagnostic): Remove assert.
gcc/testsuite/ChangeLog:
* g++.dg/ext/is_convertible5.C: New test.
next prev parent reply other threads:[~2023-04-13 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 18:54 [Bug c++/109277] New: " marxin at gcc dot gnu.org
2023-03-24 18:54 ` [Bug c++/109277] " marxin at gcc dot gnu.org
2023-03-24 20:14 ` pinskia at gcc dot gnu.org
2023-03-24 20:20 ` [Bug libstdc++/109277] " pinskia at gcc dot gnu.org
2023-03-24 20:35 ` [Bug c++/109277] " pinskia at gcc dot gnu.org
2023-03-24 20:43 ` pinskia at gcc dot gnu.org
2023-03-24 20:47 ` pinskia at gcc dot gnu.org
2023-03-24 20:49 ` pinskia at gcc dot gnu.org
2023-03-24 20:53 ` pinskia at gcc dot gnu.org
2023-03-24 21:03 ` pinskia at gcc dot gnu.org
2023-03-24 21:07 ` redi at gcc dot gnu.org
2023-03-25 14:20 ` ppalka at gcc dot gnu.org
2023-03-25 14:30 ` ppalka at gcc dot gnu.org
2023-03-27 7:06 ` rguenth at gcc dot gnu.org
2023-04-04 3:33 ` jason at gcc dot gnu.org
2023-04-13 15:41 ` jason at gcc dot gnu.org
2023-04-13 18:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-13 19:06 ` jason 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-109277-4-uxWWhS0eVl@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).