public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Fri, 24 Mar 2023 20:47:01 +0000	[thread overview]
Message-ID: <bug-109277-4-bZ1Vvaxjff@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 #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> The difference is is_convertible definition.
> 12:
>   template<typename _From, typename _To>
>     struct is_convertible
>     : public __is_convertible_helper<_From, _To>::type
>     { };
> 
> 
> 13:
>   template<typename _From, typename _To>
>     struct is_convertible
>     : public __bool_constant<__is_convertible(_From, _To)>
>     { };
> 
> So it might be a front-end issue after all.

and yes that is definitely the difference here. If I add back the
__is_convertible_helper and use that for is_convertible to the GCC 13
preprocessed source, the code then compiles.

  parent reply	other threads:[~2023-03-24 20:47 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 [this message]
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
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-bZ1Vvaxjff@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).