"Last minute" fix for libstdc++/20806

Paolo Carlini pcarlini@suse.de
Fri Apr 8 11:05:00 GMT 2005


Hi everyone,

the below is what I have regtested, to be safe, on x86-linux. This
approach is reported to fix the problem on mingw32. Generally, I
consider the patch very safe on anything != mingw32 and would take the
risk of applying it very close to the release of 4.0, if the mingw32
maintainer approves its specific bits.

A few observations:
1- If we really want it, we must be *very* quick: a complete code freeze
for 4.0 is scheduled this week-end.
2- I'm not sure whether __CYGWIN__ should be also taken care elsewhere,
besides the newlib config.
3- In any case, I will *not* be able to commit patches during most of
next week: therefore, in case the release manager allows a late commit,
someone else will have to do it (Benjamin? Thanks in advance, in case)

Paolo.

/////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CL_20806
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050408/9320bc0c/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_20806
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050408/9320bc0c/attachment-0001.ksh>


More information about the Libstdc++ mailing list