public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110323] [11/12/13/14 Regression] Code for explicit instantiation of template method of template class not generated Date: Tue, 05 Mar 2024 21:39:26 +0000 [thread overview] Message-ID: <bug-110323-4-JpXTVEkxkO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110323-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110323 --- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Ah -- if we walk into TYPE_CONTEXT (t) (here: struct conditional), then in min_vis_r we determine the visibility as VISIBILITY_ANON. Without it, it remains VISIBILITY_DEFAULT.
next prev parent reply other threads:[~2024-03-05 21:39 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-20 15:57 [Bug c++/110323] New: Code for explicit instantiation of template method of template class stlim0727 at gmail dot com 2023-06-20 16:12 ` [Bug c++/110323] [11/12/13/14 Regression] Code for explicit instantiation of template method of template class not generated pinskia at gcc dot gnu.org 2024-03-05 20:47 ` mpolacek at gcc dot gnu.org 2024-03-05 20:49 ` mpolacek at gcc dot gnu.org 2024-03-05 21:39 ` mpolacek at gcc dot gnu.org [this message] 2024-03-05 22:56 ` mpolacek at gcc dot gnu.org 2024-03-06 14:53 ` mpolacek at gcc dot gnu.org 2024-03-07 15:23 ` mpolacek at gcc dot gnu.org 2024-03-08 17:25 ` ppalka at gcc dot gnu.org 2024-03-08 17:43 ` mpolacek at gcc dot gnu.org 2024-03-08 17:47 ` mpolacek at gcc dot gnu.org 2024-03-21 17:54 ` cvs-commit at gcc dot gnu.org 2024-03-21 17:55 ` [Bug c++/110323] [11/12/13 " mpolacek 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-110323-4-JpXTVEkxkO@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).