This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Mingw-users] [patch] --enable-dynamic-string default for mingw-w64
On 9/25/2011 11:14 AM, Cesar Strauss wrote:
> On 09/25/2011 02:36 AM, JonY wrote:
>> Ping, mingw.org OK with this?
>
> Please, enable this only for w64 flavor. We (mingw.org) are not
> building our libstdc++ with this configure option, and there are no
> plans to change it.
>
> I quote my reasoning:
>
> On 09/20/2011 11:56 PM, Cesar Strauss wrote:
>> 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
Well, I disagree -- I think correctness (e.g. actually working, even if
you are so gauche as to link statically) trumps working faster -- as a
default setting. (And I'd rather see some actual numbers for
comparison: how MUCH faster, under what workloads? Is it truly
significant enough to put up with breakage when linking statically?)
But...Cesar is mingw.org's gcc maintainer, not me. So what Cesar says,
goes as far as mingw.org is concerned.
I note one other comment in the referenced bugzilla thread, where Paolo
mentions that the ABI will break for C++1x (libstdc++7?) anyway, and
that in the "new" string implementation this issue will be not actually
be an issue. Is that 2009 statement still operative?
(I think we [mingw.org] still need to consider consolidating as many of
the expected ABI changes as possible for the 4.7 release, since we
already expect thiscall to become the default at that time, right? Even
though 'switching' to --enable-fully-dynamic-string is no longer on the
menu for i?86-pc-mingw32)
--
Chuck