carlini at oracle dot com"
Sent: Monday, July 20, 2009 4:25 PM
To:
Subject: [Bug libstdc++/40802] Libstdc++ is broken for win32 host
>
>
> --- Comment #7 from paolo dot carlini at oracle dot com 2009-07-20
> 20:25 ---
> Let's also add a mingw maintainer. In f
--- Comment #7 from paolo dot carlini at oracle dot com 2009-07-20 20:25
---
Let's also add a mingw maintainer. In fact, I think this PR should be just
recategorized as , the generic libstdc++ code is very unlikely to be at
fault here.
--
paolo dot carlini at oracle dot com changed:
--- Comment #6 from paolo dot carlini at oracle dot com 2009-07-20 20:02
---
No vacations, eh? I understand... ;) Anyway, since you don't trust me, about
the general points I'm making, let's CC Benjamin, I take no offense (it's the
two of us for the library, in general)
--
paolo dot
a lot.
--
From: "paolo dot carlini at oracle dot com"
Sent: Monday, July 20, 2009 3:47 PM
To:
Subject: [Bug libstdc++/40802] Libstdc++ is broken for win32 host
>
>
> --- Comment #4 from paolo dot carlini at oracle dot com 2009-07-2
--- Comment #4 from paolo dot carlini at oracle dot com 2009-07-20 19:47
---
Hey Peter, you are free to do whatever you want. Just wanted to clarify that
the GCC developers are routinely testing for many other targets, both 32-bit
and 64-bit, in general, and there the problem doesn't s
the purpose of this forum again? Of
course, I have, to the best of my ability, ruled out my own system as the
source of the problem.
--
From: "paolo dot carlini at oracle dot com"
Sent: Sunday, July 19, 2009 7:53 AM
To:
Subject: [Bug libstd
--- Comment #2 from paolo dot carlini at oracle dot com 2009-07-19 11:53
---
First, you should figure out what's so special on this system vs all the other
32-bit and 64-bit systems on which the developers are routinely testing (and
which are fine, see testsresults): I see that somethin
--- Comment #1 from xenofears at gmail dot com 2009-07-19 03:55 ---
That should say **WIN64 HOST**. My Apologies.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40802
