public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65292] Template function not emitted Date: Tue, 03 Mar 2015 10:16:00 -0000 [thread overview] Message-ID: <bug-65292-4-rQLn22WDba@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65292-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65292 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Khem Raj from comment #2) > there is another file in same library where this file object resides which > uses this function and reports undefined symbol errors when linking. Then you either need to include the definition of the function template in that other file, or provide an explicit instantiation. You can't just rely on an implicit instantiation being emitted in some other .cpp file. > Has it been inlined and thrown away ? Yes. > then why the rest two were not. Because the optimizer decided to optimize them differently.
next prev parent reply other threads:[~2015-03-03 10:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65292-4@http.gcc.gnu.org/bugzilla/> 2015-03-03 6:02 ` pinskia at gcc dot gnu.org 2015-03-03 7:48 ` raj.khem at gmail dot com 2015-03-03 10:16 ` redi at gcc dot gnu.org [this message] 2015-03-05 7:36 ` gnugcc at marino dot st 2015-03-06 1:45 ` raj.khem at gmail dot com 2015-03-06 9:03 ` gnugcc at marino dot st 2015-03-06 9:05 ` gnugcc at marino dot st 2015-03-09 14:06 ` gnugcc at marino dot st
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-65292-4-rQLn22WDba@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).