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++/98356] [11/12/13/14 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 since r9-4841-g2139fd74f31449c0 Date: Thu, 07 Mar 2024 11:00:09 +0000 [thread overview] Message-ID: <bug-98356-4-sxBIr3Idun@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98356-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98356 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>: https://gcc.gnu.org/g:940586a63586941a9f2b973491afc8a15a96c98b commit r14-9357-g940586a63586941a9f2b973491afc8a15a96c98b Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Tue Mar 5 01:59:41 2024 +1100 c++: Fix ICE diagnosing incomplete type of overloaded function set [PR98356] In the linked PR the result of 'get_first_fn' is a USING_DECL against the template parameter, to be filled in on instantiation. But we don't actually need to get the first set of the member functions: it's enough to know that we have a (possibly overloaded) member function at all. PR c++/98356 gcc/cp/ChangeLog: * typeck2.cc (cxx_incomplete_type_diagnostic): Don't assume 'member' will be a FUNCTION_DECL (or something like it). gcc/testsuite/ChangeLog: * g++.dg/pr98356.C: New test. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
next prev parent reply other threads:[~2024-03-07 11:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 16:52 [Bug c++/98356] New: [9/10/11 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 gscfq@t-online.de 2020-12-18 8:48 ` [Bug c++/98356] [9/10/11 Regression] ICE in cp_parser_dot_deref_incomplete, at cp/parser.c:7899 since r9-4841-g2139fd74f31449c0 marxin at gcc dot gnu.org 2020-12-18 12:43 ` nathan at gcc dot gnu.org 2021-01-05 8:34 ` rguenth at gcc dot gnu.org 2021-06-01 8:19 ` [Bug c++/98356] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug c++/98356] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug c++/98356] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-04 23:41 ` mpolacek at gcc dot gnu.org 2024-03-07 11:00 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-10 23:16 ` [Bug c++/98356] [11/12/13 " law 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-98356-4-sxBIr3Idun@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).