On 09/26/2011 02:34 AM, Charles Wilson wrote:
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
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 reason
On 9/25/2011 23:20, Paolo Carlini wrote:
> On 09/25/2011 05:14 PM, Cesar Strauss wrote:
>> 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
>>> opt
2011/9/25 Paolo Carlini :
> On 09/25/2011 05:14 PM, Cesar Strauss wrote:
>>
>> 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
>>> optimizatio
On 09/25/2011 05:14 PM, Cesar Strauss wrote:
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-li
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.
>> Otherw
On 9/23/2011 22:15, Paolo Carlini wrote:
> On 09/23/2011 03:59 PM, Paolo Carlini wrote:
>> On 09/23/2011 03:46 PM, Paolo Carlini wrote:
>>> On 09/23/2011 11:39 AM, JonY wrote:
Ping, any updates?
>>> I'm wondering if it wouldn't be cleaner to handle this in the
>>> appropriate config/os/ heade
On 09/23/2011 03:59 PM, Paolo Carlini wrote:
On 09/23/2011 03:46 PM, Paolo Carlini wrote:
On 09/23/2011 11:39 AM, JonY wrote:
Ping, any updates?
I'm wondering if it wouldn't be cleaner to handle this in the
appropriate config/os/ headers, something like (with a good comment
before!):
#ifnde
On 09/23/2011 03:46 PM, Paolo Carlini wrote:
On 09/23/2011 11:39 AM, JonY wrote:
Ping, any updates?
I'm wondering if it wouldn't be cleaner to handle this in the
appropriate config/os/ headers, something like (with a good comment
before!):
#ifndef _GLIBCXX_FULLY_DYNAMIC_STRING
#define _GLIBC
On 9/23/2011 21:46, Paolo Carlini wrote:
> On 09/23/2011 11:39 AM, JonY wrote:
>> Ping, any updates?
> I'm wondering if it wouldn't be cleaner to handle this in the
> appropriate config/os/ headers, something like (with a good comment
> before!):
>
> #ifndef _GLIBCXX_FULLY_DYNAMIC_STRING
> #defin
On 09/23/2011 11:39 AM, JonY wrote:
Ping, any updates?
I'm wondering if it wouldn't be cleaner to handle this in the
appropriate config/os/ headers, something like (with a good comment
before!):
#ifndef _GLIBCXX_FULLY_DYNAMIC_STRING
#define _GLIBCXX_FULLY_DYNAMIC_STRING
#endif
Paolo.
On 9/21/2011 17:08, xunxun wrote:
> 于 2011/9/21 10:56, Cesar Strauss 写道:
>> 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
于 2011/9/21 10:56, Cesar Strauss 写道:
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 st
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:
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 n
14 matches
Mail list logo
