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 libstdc++/51813] [4.7 Regression] -fvisibility=hidden causes std::codecvt members to be undefined
Date: Fri, 13 Jan 2012 16:53:00 -0000 [thread overview]
Message-ID: <bug-51813-4-QmC33sUT94@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51813-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51813
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-13 16:43:12 UTC ---
(In reply to comment #3)
> What do we want to do about C library visibility?
We can't redeclare all the types with default visibility, because we don't know
if e.g. mbstate_t is just a typedef.
This appears to fix it, but would it need to be done for any explicit
instantation relying on non-builtin types defined outside libstdc++?
extern template
__attribute__((visibility("default")))
const codecvt<wchar_t, char, mbstate_t>&
use_facet<codecvt<wchar_t, char, mbstate_t> >(const locale&);
next prev parent reply other threads:[~2012-01-13 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 14:38 [Bug c++/51813] New: " sefi@s-e-f-i.de
2012-01-13 12:03 ` [Bug c++/51813] [4.7 Regression] " paolo.carlini at oracle dot com
2012-01-13 15:59 ` jason at gcc dot gnu.org
2012-01-13 16:41 ` [Bug libstdc++/51813] " jason at gcc dot gnu.org
2012-01-13 16:43 ` paolo.carlini at oracle dot com
2012-01-13 16:53 ` redi at gcc dot gnu.org [this message]
2012-01-13 17:01 ` paolo.carlini at oracle dot com
2012-01-13 17:05 ` jason at gcc dot gnu.org
2012-01-13 17:24 ` [Bug c++/51813] " jason at gcc dot gnu.org
2012-01-13 18:10 ` jason at gcc dot gnu.org
2012-01-13 18:40 ` jason 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-51813-4-QmC33sUT94@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).