public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97399] [9/10/11 Regression] g++ 9.3 cannot compile SFINAE code with separated declaration and definition, g++ 7.3 compiles Date: Wed, 20 Jan 2021 20:00:46 +0000 [thread overview] Message-ID: <bug-97399-4-FWb4vyJpMs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97399-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97399 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org CC| |ppalka at gcc dot gnu.org --- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> --- The alias template in the reduced testcase is a red herring, the ICE can be reproduced without it: template <bool> struct enable_if_t {}; struct tmp { template <class> static constexpr bool is_integral(); template <class E> static auto func(E, E) -> enable_if_t<tmp::is_integral<E>()>; }; template <class> constexpr bool tmp::is_integral() { return true; } int main() { tmp::func(1, 0); } Looks like the problematic hunk from r9-5972 is --- a/gcc/cp/semantics.c +++ b/gcc/cp/semantics.c @@ -2096,7 +2096,8 @@ finish_qualified_id_expr (tree qualifying_class, { /* See if any of the functions are non-static members. */ /* If so, the expression may be relative to 'this'. */ - if (!shared_member_p (expr) + if ((type_dependent_expression_p (expr) + || !shared_member_p (expr)) && current_class_ptr && DERIVED_FROM_P (qualifying_class, current_nonlambda_class_type ()))
next prev parent reply other threads:[~2021-01-20 20:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-13 9:58 [Bug c++/97399] New: " renlin at gcc dot gnu.org 2020-10-13 9:58 ` [Bug c++/97399] " renlin at gcc dot gnu.org 2020-10-13 11:02 ` [Bug c++/97399] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2020-10-13 14:10 ` marxin at gcc dot gnu.org 2021-01-14 9:25 ` rguenth at gcc dot gnu.org 2021-01-20 20:00 ` ppalka at gcc dot gnu.org [this message] 2021-01-23 5:25 ` cvs-commit at gcc dot gnu.org 2021-01-23 5:25 ` [Bug c++/97399] [9/10 " ppalka at gcc dot gnu.org 2021-04-10 20:33 ` cvs-commit at gcc dot gnu.org 2021-06-01 8:18 ` rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug c++/97399] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 9:08 ` rguenth 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-97399-4-FWb4vyJpMs@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).