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++/106849] internal compiler error: tree check: expected none of template_decl, have template_decl in do_nonmember_using_decl, at cp/name-lookup.cc:4841
Date: Tue, 14 Nov 2023 19:43:31 +0000	[thread overview]
Message-ID: <bug-106849-4-L7wuuqQ2Jr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106849-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106849

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:

https://gcc.gnu.org/g:5b9ecce87e8f315e2681743d75401991cdfefa71

commit r14-5460-g5b9ecce87e8f315e2681743d75401991cdfefa71
Author: Nathaniel Shead <nathanieloshead@gmail.com>
Date:   Thu Nov 9 19:05:09 2023 -0500

    c++: Fix exported using decls of templates

    We need to look at DECL_TEMPLATE_RESULT to get the module attachment.

            PR c++/106849

    gcc/cp/ChangeLog:

            * name-lookup.cc (do_nonmember_using_decl): Handle
            TEMPLATE_DECLs when checking module attachment.

    gcc/testsuite/ChangeLog:

            * g++.dg/modules/using-9.C: New test.

    Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
    Signed-off-by: Nathan Sidwell <nathan@acm.org>

  parent reply	other threads:[~2023-11-14 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 13:50 [Bug c++/106849] New: " redi at gcc dot gnu.org
2023-11-02 19:03 ` [Bug c++/106849] " pinskia at gcc dot gnu.org
2023-11-02 19:05 ` davidfromonline at gmail dot com
2023-11-02 19:06 ` davidfromonline at gmail dot com
2023-11-14 19:43 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-15  6:31 ` sjames at gcc dot gnu.org
2024-02-11 13:33 ` nshead 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-106849-4-L7wuuqQ2Jr@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: link
Be 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).