public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davidfromonline at gmail dot com" <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: Thu, 02 Nov 2023 19:06:32 +0000 [thread overview] Message-ID: <bug-106849-4-GPVT1rarWc@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 #3 from David Stone <davidfromonline at gmail dot com> --- Oh, as per https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112355#c3 it's just that the 13.2 build isn't checked, so it's not a new bug.
next prev parent reply other threads:[~2023-11-02 19:06 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 [this message] 2023-11-14 19:43 ` cvs-commit at gcc dot gnu.org 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-GPVT1rarWc@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).