(Shouldn't this be on the libstdc++ list?)
On 6 June 2010 19:02, Doug Semler wrote:
>
> So...would you consider this a bug in the documentation, or a bug in
> the library?
I would say the docs, and only partly because it's easier to fix ;-)
> And even if it's a bug in the documentation, it will
Hi,
So...would you consider this a bug in the documentation, or a bug in
the library? And even if it's a bug in the documentation, it will
eventually have to be fixed for c++0x, yes?
Maybe in the documentation, I'm not sure, the documentation is lacking
in various areas I'm afraid, and patc
On Sun, Jun 6, 2010 at 12:03 PM, Paolo Carlini wrote:
>
>> Before I entered a bug I wanted to see if I am actually interpreting
>> this correctly.
>
> Assuming you are, the issue doesn't qualify for Bugzilla, because nobody
> claims to have implemented this section of c++0x.
>
> Paolo
Well, it do
Before I entered a bug I wanted to see if I am actually interpreting
this correctly.
Assuming you are, the issue doesn't qualify for Bugzilla, because
nobody claims to have implemented this section of c++0x.
Paolo
While investigating a multithread segfault on mingw32 systems, I
discovered that the cause of the problem is a data race introduced in
the config/locale/generic/c_locale.cc and friends.
There are several data races that can occur. Note that these races
are INDEPENDENT of the thread safety of setl
