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++/90711] [9/10 Regression] Failing SFINAE from unrelated struct since r9-6794 Date: Mon, 30 Mar 2020 21:16:53 +0000 [thread overview] Message-ID: <bug-90711-4-ksUAo5loas@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90711 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:5830f753559f25a5dabcc3507bffa611c6b575a6 commit r10-7465-g5830f753559f25a5dabcc3507bffa611c6b575a6 Author: Jason Merrill <jason@redhat.com> Date: Mon Mar 30 16:09:43 2020 -0400 c++: Fix comparison of fn() and ns::fn() [PR90711] The resolution of CWG issue 1321 clarified that when deciding whether two expressions involving template parameters are equivalent, two dependent function calls where the function is named with an unqualified-id are considered to be equivalent if the name is the same, even if unqualified lookup finds different sets of functions. We were wrongly treating qualified-ids the same way, so that EXISTS and test::EXISTS were considered to be equivalent even though they are looking up the name in different scopes. This also causes a mangling bug, but I don't think it's safe to fix that for GCC 10; this patch just fixes the comparison. gcc/cp/ChangeLog 2020-03-30 Jason Merrill <jason@redhat.com> PR c++/90711 * tree.c (cp_tree_equal) [CALL_EXPR]: Compare KOENIG_LOOKUP_P. (called_fns_equal): Check DECL_CONTEXT.
next prev parent reply other threads:[~2020-03-30 21:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90711-4@http.gcc.gnu.org/bugzilla/> 2020-03-23 17:50 ` ppalka at gcc dot gnu.org 2020-03-27 21:44 ` jason at gcc dot gnu.org 2020-03-30 21:16 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-31 17:04 ` cvs-commit at gcc dot gnu.org 2020-03-31 17:47 ` jason at gcc dot gnu.org 2020-04-03 15:30 ` cvs-commit 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-90711-4-ksUAo5loas@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).