public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/42608] [4.4/4.5 Regression] Undefined reference not reported in case of explicit template instantiation Date: Fri, 08 Jan 2010 12:06:00 -0000 [thread overview] Message-ID: <20100108120612.23799.qmail@sourceware.org> (raw) In-Reply-To: <bug-42608-18628@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jakub at gcc dot gnu dot org 2010-01-08 12:06 ------- Yeah, there are several reasons why DECL_WEAK may be set, but only when it is because of weak attribute or #pragma weak we want to add it to weak_decls. For vague linkage, or weakref attribute we don't want to do that. I wonder whether we couldn't add weak attribute in apply_pragma_weak and just add to weak_decls decls that have that attribute. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42608
next prev parent reply other threads:[~2010-01-08 12:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-04 13:58 [Bug c++/42608] New: " bastien_emmanuel at yahoo dot fr 2010-01-04 14:19 ` [Bug c++/42608] [4.4/4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-05 23:02 ` jason at gcc dot gnu dot org 2010-01-05 23:14 ` jason at gcc dot gnu dot org 2010-01-07 14:47 ` rguenth at gcc dot gnu dot org 2010-01-07 19:50 ` jason at gcc dot gnu dot org 2010-01-08 12:06 ` jakub at gcc dot gnu dot org [this message] 2010-01-08 13:42 ` jakub at gcc dot gnu dot org 2010-01-14 22:41 ` jakub at gcc dot gnu dot org 2010-01-14 22:47 ` jakub at gcc dot gnu dot org 2010-01-14 23:20 ` jakub at gcc dot gnu dot 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=20100108120612.23799.qmail@sourceware.org \ --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).