public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "herring at lanl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107906] New: Function template specialization given weak rather than local symbol Date: Tue, 29 Nov 2022 06:44:58 +0000 [thread overview] Message-ID: <bug-107906-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107906 Bug ID: 107906 Summary: Function template specialization given weak rather than local symbol Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: herring at lanl dot gov Target Milestone: --- Current trunk, given <https://godbolt.org/z/aoMecfhqb> template<class> using X=int; namespace { template<class> using Y=int; } template<template<class> class Q> void f() {} template void f<X>(); void (*fp)()=f<Y>; emits weak symbols for both specializations of f, despite the fact that a different "void f<(anonymous namespace)::Y>()" might be defined in another translation unit (perhaps as an explicit specialization).
next reply other threads:[~2022-11-29 6:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 6:44 herring at lanl dot gov [this message] 2022-11-29 8:19 ` [Bug c++/107906] " rguenth at gcc dot gnu.org 2022-11-29 8:57 ` [Bug c++/107906] linkage of template not taken into account pinskia at gcc dot gnu.org 2022-11-30 15:46 ` herring at lanl dot gov 2022-11-30 15:52 ` redi at gcc dot gnu.org 2022-12-29 3:07 ` pinskia at gcc dot gnu.org 2023-12-21 18:53 ` cvs-commit at gcc dot gnu.org 2023-12-21 18:58 ` [Bug c++/107906] linkage of alias " ppalka 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-107906-4@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).