public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka 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: Sat, 25 Mar 2023 14:30:11 +0000 [thread overview]
Message-ID: <bug-109277-4-KJBAdreGG1@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
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection, |
|needs-reduction |
--- Comment #10 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Thus started with the move to use the built-in __is_convertible in
std::is_convertible, r13-2883-gaf85ad891703db
(In reply to Patrick Palka from comment #9)
> One fix is to define a move constructor for TNode, which causes GCC's
> perfect candidate optimization (r11-7287-g187d0d5871b1fa) to kick in and
> avoid considering the template candidate #1. Another fix is to use
> std::conjunction/disjunction in is_subtype so that the condition properly
> short-circuits (is_base_of<T, T> is true even for incomplete T).
Note that the first proposed fix would just paper over the UB, whereas the
second fix would eliminate it IIUC.
next prev parent reply other threads:[~2023-03-25 14:30 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 [this message]
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
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-KJBAdreGG1@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).