From: Benjamin Kosnik <bkoz@redhat.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: libstdc++@gcc.gnu.org, GCC Patches <gcc-patches@gcc.gnu.org>,
Danny Smith <dansmister@gmail.com>,
"Aaron W. LaFramboise (GCC)" <aaronavay62@aaronwl.com>,
Kai Tietz <ktietz70@googlemail.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>
Subject: Re: Libstdc++ as DLL on windows, alternative approach [was Re: cygwin patch review]
Date: Thu, 19 Nov 2009 17:39:00 -0000 [thread overview]
Message-ID: <20091119093347.797df3ff@mcgee.artheist.org> (raw)
In-Reply-To: <4AFC8EC3.10502@gmail.com>
> Ok, so as we discussed before, this doesn't currently work.
> However it does sound like the right thing to do, so I've spun a new
> version of the patch that applies dllimport to the namespace. We
> could commit this and then open a PR about dllimport not working on
> namespaces. It's much smaller and cleaner than the version that adds
> markup everywhere, but I doubt I'll be able to fix the
> dllimport-vs-namespace bug in time for 4.5. That's not the end of
> the world; getting dllimport right is a good optimisation, but we can
> live with the compromise of auto-import for now.
I like this plan. What's the PR number? And can you affix your
patch from here to it:
http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00979.html
Thanks.
> Initial test results (c and c++ only) are posted(*) and look right,
> but I'll do a clean run on the same source revision for comparison
> anyway. Note that I had to patch various testsuite/lib/ files to
> avoid the current utf-8 problem(**) that would otherwise have
> provoked many spurious 'excess errors' warnings. That'll be the
> subject of a separate patch, I'll do the clean run using them as well
> so the comparison is fair.
It looks like (in later messages) you have an updated patch. But your
updated results here looks great:
http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg01084.html
> libstdc++-v3/ChangeLog:
>
> * libstdc++-v3/acinclude.m4 (GLIBCXX_ENABLE_SYMVERS): Don't
> disable on PE targets.
> * libstdc++-v3/configure: Regenerate.
> * libstdc++-v3/configure.host: Add libtool DLL options for
> Cygwin and MinGW platforms.
>
> * libstdc++-v3/include/bits/c++config
> (_GLIBCXX_VISIBILITY_ATTR): On platforms that don't support
> visibility, allow them to declare a macro _GLIBCXX_PSEUDO_VISIBILITY
> that is applied in place of visibility.
>
> * libstdc++-v3/config/os/newlib/os_defines.h
> (_GLIBCXX_PSEUDO_VISIBILITY_default): New macro for dllimport.
> (_GLIBCXX_PSEUDO_VISIBILITY_hidden): New empty macro.
> (_GLIBCXX_PSEUDO_VISIBILITY): Evaluate to one of the above.
> * libstdc++-v3/config/os/mingw32/os_defines.h
> (_GLIBCXX_PSEUDO_VISIBILITY_default,
> _GLIBCXX_PSEUDO_VISIBILITY_hidden,
> _GLIBCXX_PSEUDO_VISIBILITY): Likewise.
>
> So, is this any more like OK for head?
Yes, exactly. Thanks. This is OK with me.
best,
benjamin
next prev parent reply other threads:[~2009-11-19 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091019092452.2e271791@mcgee.artheist.org>
2009-11-12 22:33 ` Dave Korn
2009-11-16 2:57 ` Dave Korn
2009-11-16 3:34 ` Danny Smith
2009-11-16 3:37 ` Dave Korn
2009-11-19 1:25 ` Dave Korn
2009-11-19 17:39 ` Benjamin Kosnik [this message]
2009-11-20 16:56 ` Dave Korn
2009-11-21 6:34 ` Danny Smith
2009-11-23 17:47 ` Benjamin Kosnik
2009-11-30 20:21 ` Dave Korn
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=20091119093347.797df3ff@mcgee.artheist.org \
--to=bkoz@redhat.com \
--cc=aaronavay62@aaronwl.com \
--cc=dansmister@gmail.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=libstdc++@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).