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++/106784] Add __is_convertible built-in Date: Mon, 26 Sep 2022 16:42:25 +0000 [thread overview] Message-ID: <bug-106784-4-Jos0PaXmBg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106784-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106784 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:be4b32b9ef69b86b662cb7511b48cd1048a55403 commit r13-2879-gbe4b32b9ef69b86b662cb7511b48cd1048a55403 Author: Marek Polacek <polacek@redhat.com> Date: Mon Sep 26 10:21:38 2022 -0400 c++: Instantiate less when evaluating __is_convertible Jon reported that evaluating __is_convertible in a test led to instantiating something ill-formed and so we failed to compile the test. __is_convertible doesn't and shouldn't need to instantiate so much, so let's limit it with a cp_unevaluated guard. Use a helper function to implement both built-ins. PR c++/106784 gcc/cp/ChangeLog: * method.cc (is_convertible_helper): New. (is_convertible): Use it. (is_nothrow_convertible): Likewise. gcc/testsuite/ChangeLog: * g++.dg/ext/is_convertible3.C: New test. * g++.dg/ext/is_nothrow_convertible3.C: New test.
next prev parent reply other threads:[~2022-09-26 16:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-31 10:41 [Bug c++/106784] New: " redi at gcc dot gnu.org 2022-08-31 13:38 ` [Bug c++/106784] " mpolacek at gcc dot gnu.org 2022-08-31 14:05 ` mpolacek at gcc dot gnu.org 2022-09-01 16:26 ` redi at gcc dot gnu.org 2022-09-20 21:24 ` mpolacek at gcc dot gnu.org 2022-09-21 0:02 ` redi at gcc dot gnu.org 2022-09-23 16:17 ` cvs-commit at gcc dot gnu.org 2022-09-23 16:18 ` mpolacek at gcc dot gnu.org 2022-09-24 14:10 ` redi at gcc dot gnu.org 2022-09-26 16:42 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-29 17:44 ` pinskia 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-106784-4-Jos0PaXmBg@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).