On 09/25/2011 02:36 AM, JonY wrote: > On 9/23/2011 22:15, Paolo Carlini wrote: >> I hope you got the basic point anyway, sorry about the confusion >> ;) >> >> I meant that if the user configuring doesn't pass anything to >> configure, then _GLIBCXX_FULLY_DYNAMIC_STRING remains undefined. >> Otherwise, zero is set in the acinclude.m4 procedure for no fully >> dynamic string and one for fully dynamic string. Then we have >> >> #ifndef _GLIBCXX_FULLY_DYNAMIC_STRING #define >> _GLIBCXX_FULLY_DYNAMIC_STRING 1 #endif >> >> in the mingw config/os (with a good comment before!) and, in the >> basic_string.* headers we use: >> >> #if _GLIBCXX_FULLY_DYNAMIC_STRING == 1 >> >> This is a standard pattern in configuries, anyway... >> >> Paolo. >> > > 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 Thanks, Cesar
