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++/95066] [C++ 20] Incorrect successful compilation with a conditional explicit Date: Wed, 13 May 2020 20:26:13 +0000 [thread overview] Message-ID: <bug-95066-4-UEKEBvnoJj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95066 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:661232da72d29f8f2385d5f588727beb74360144 commit r11-371-g661232da72d29f8f2385d5f588727beb74360144 Author: Marek Polacek <polacek@redhat.com> Date: Mon May 11 18:28:19 2020 -0400 c++: explicit(bool) malfunction with dependent expression [PR95066] I forgot to set DECL_HAS_DEPENDENT_EXPLICIT_SPEC_P when merging two function declarations and as a sad consequence, we never tsubsted the dependent explicit-specifier in tsubst_function_decl, leading to disregarding the explicit-specifier altogether, and wrongly accepting this test. PR c++/95066 * decl.c (duplicate_decls): Set DECL_HAS_DEPENDENT_EXPLICIT_SPEC_P. * g++.dg/cpp2a/explicit16.C: New test.
next prev parent reply other threads:[~2020-05-13 20:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 17:50 [Bug c++/95066] New: [C++ 20] Incorrect valid " ojman101 at protonmail dot com 2020-05-11 17:57 ` [Bug c++/95066] " ojman101 at protonmail dot com 2020-05-11 18:26 ` [Bug c++/95066] [C++ 20] Incorrect successful " mpolacek at gcc dot gnu.org 2020-05-11 22:00 ` mpolacek at gcc dot gnu.org 2020-05-11 23:07 ` mpolacek at gcc dot gnu.org 2020-05-13 20:26 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-11 20:33 ` cvs-commit at gcc dot gnu.org 2020-06-11 20:33 ` mpolacek 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-95066-4-UEKEBvnoJj@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).