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:43:41 +0000 [thread overview] Message-ID: <bug-109277-4-uBac3dAxMb@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 #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Though the code might be undefined ... 20.15.6/5 says: ``` The predicate condition for a template specialization is_convertible<From, To> shall be satisfied if and only if the return expression in the following code would be well-formed, including any implicit conversions to the return type of the function: To test() { return declval<From>(); } [Note: This requirement gives well-defined results for reference types, void types, array types, and function types. — end note] Access checking is performed in a context unrelated to To and From. Only the validity of the immediate context of the expression of the return statement (8.7.3) (including initialization of the returned object or reference) is considered. [Note: The initialization can result in side effects such as the instantiation of class template specializations and function template specializations, the generation of implicitly-defined functions, and so on. Such side effects are not in the “immediate context” and can result in the program being ill-formed. — end note] ``` I am not 100% sure but I suspect this is just ill-formed code which was not rejected before but is now using the builtin rather than the template form ...
next prev parent reply other threads:[~2023-03-24 20:43 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 [this message] 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 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-uBac3dAxMb@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: linkBe 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).