This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/44679] [4.5/4.6 regression] 30_threads/condition_variable_any/cons/1.cc fails with -fstack-protector (built with 4.4, run with 4.5)
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jun 2010 16:03:27 -0000
- Subject: [Bug libstdc++/44679] [4.5/4.6 regression] 30_threads/condition_variable_any/cons/1.cc fails with -fstack-protector (built with 4.4, run with 4.5)
- References: <bug-44679-11764@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from rguenth at gcc dot gnu dot org 2010-06-28 16:03 -------
(In reply to comment #2)
> condition_variable_any was completely broken in 4.4 and its ABi changed when we
> implemented it for real. Obviously we can't preserve ABI between a broken,
> incomplete implementation and a working one, so I'm not really worried about
> this "bug". If anyone was able to use the condition_variable_any in 4.4 I'd
> like to know how they did it!
We should avoid exporting symbols for something that is broken or supposed
to change its ABI. I think this is what was done in the past, why wasn't
it done here?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44679