On 9/20/2011 12:29 PM, Charles Wilson wrote:
On 9/20/2011 10:12 AM, Kai Tietz wrote:
2011/9/20 Charles Wilson<x...@yyy.com>:
So, this would be a change in current mingw.org behavior. I *was*
under the impression that this workaround for the old "can't pass
empty strings across DLL boundary" problem[1] was no longer necessary
in the gcc-4.x era, but I haven't tested the proposition. Was I wrong
about that?
Yes. If you read last comment of the thread you are citing, then you
would notice that for static-libstdc++ version the issue is still
present. So to allow users to use also static-libstdc++ variant, this
option is still necessary.
Thanks for the clarification. So, we (mingw.org) really should have
been using this all along, to support users of -static-libstdc++
Please let me present an opposing view.
On the one hand, according to comment 4 of [1], by using
--enable-fully-dynamic-string, all other users will miss a very good
optimization. On the other hand, these users of -static-libstdc++ are
mixing shared and static libraries, which isn't a good idea in general
anyway, is it?
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196
Regards,
Cesar
