public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
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)
Date: Mon, 28 Jun 2010 16:03:00 -0000 [thread overview]
Message-ID: <20100628160327.11450.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44679-11764@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2010-06-28 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 10:19 [Bug libstdc++/44679] New: " doko at ubuntu dot com
2010-06-26 11:27 ` [Bug libstdc++/44679] " paolo dot carlini at oracle dot com
2010-06-26 14:01 ` redi at gcc dot gnu dot org
2010-06-26 14:51 ` redi at gcc dot gnu dot org
2010-06-28 16:03 ` rguenth at gcc dot gnu dot org [this message]
2010-06-28 16:13 ` paolo dot carlini at oracle dot com
2010-06-28 16:14 ` paolo dot carlini at oracle dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100628160327.11450.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).