public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35688] template visibility not overridden by template arguments
Date: Mon, 11 Feb 2013 15:45:00 -0000	[thread overview]
Message-ID: <bug-35688-4-nZrkzkidsx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35688-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35688

--- Comment #15 from Jason Merrill <jason at gcc dot gnu.org> 2013-02-11 15:44:51 UTC ---
(In reply to comment #13)
> I don't understand why fully declared templates like Boost's shared_ptr have a
> visibility at all.

I'm not sure why they would.  Are you compiling with -fvisibility=hidden?  If
so, you need to explicitly give everything that you want to be exported the
appropriate visibility.

> Do I've to change my code or is this a regression or is it Boost's fault?

You might wrap the #includes in

#pragma GCC visibility push(default)
#pragma GCC visibility pop

to give the Boost library all default visibility.


      parent reply	other threads:[~2013-02-11 15:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-35688-4@http.gcc.gnu.org/bugzilla/>
2010-10-27 22:10 ` [Bug c++/35688] template visibility botch pinskia at gcc dot gnu.org
2011-11-06 12:14 ` [Bug c++/35688] template visibility not overridden by template arguments paolo.carlini at oracle dot com
2011-11-06 13:20 ` jason at gcc dot gnu.org
2011-11-06 13:22 ` jason at gcc dot gnu.org
2011-11-06 20:37 ` jason at gcc dot gnu.org
2011-11-06 21:14 ` paolo.carlini at oracle dot com
2011-11-07  4:41 ` jason at gcc dot gnu.org
2011-11-07  9:24 ` vincenzo.innocente at cern dot ch
2011-11-07  9:39 ` vincenzo.innocente at cern dot ch
2011-11-07 17:55 ` jason at gcc dot gnu.org
2011-11-07 21:18 ` jason at gcc dot gnu.org
2011-11-07 21:25 ` jason at gcc dot gnu.org
2011-11-08  8:53 ` vincenzo.innocente at cern dot ch
2012-12-08 12:10 ` Woebbeking at web dot de
2013-02-10 15:50 ` Woebbeking at web dot de
2013-02-11 15:45 ` jason at gcc dot gnu.org [this message]

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-35688-4-nZrkzkidsx@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: link
Be 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).