public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52839] double free or corruption running tr1/.../default_weaktoshared.exe Date: Tue, 10 Apr 2012 23:53:00 -0000 [thread overview] Message-ID: <bug-52839-4-u7QyGVB5Ba@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52839-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52839 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.7.1 |--- --- Comment #22 from Alan Modra <amodra at gmail dot com> 2012-04-10 23:53:16 UTC --- Regarding the ABI change, would I be correct to say that the ABI was broken for powerpc by 2012-02-10 Benjamin Kosnik <bkoz@redhat.com> Jonathan Wakely <jwakely.gcc@gmail.com> since that particular patch introduced the dependency on having long long atomics? If I understand correctly, before that change code would use sync builtins on powerpc throughout. So code compiled before that date won't behave correctly using a current libstdc++.so, which now uses mutexes. I'm not trying to apportion blame, just pointing out that making libstdc++ use atomics on powerpc *fixes* an ABI breakage for the great majority of cases.
next prev parent reply other threads:[~2012-04-10 23:53 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-03 2:01 [Bug libstdc++/52839] New: " amodra at gmail dot com 2012-04-03 8:30 ` [Bug libstdc++/52839] " redi at gcc dot gnu.org 2012-04-03 9:19 ` redi at gcc dot gnu.org 2012-04-03 21:34 ` redi at gcc dot gnu.org 2012-04-04 0:20 ` redi at gcc dot gnu.org 2012-04-04 1:12 ` amodra at gmail dot com 2012-04-04 8:31 ` redi at gcc dot gnu.org 2012-04-04 9:58 ` amodra at gmail dot com 2012-04-04 10:39 ` redi at gcc dot gnu.org 2012-04-04 11:13 ` amodra at gmail dot com 2012-04-04 14:21 ` amodra at gmail dot com 2012-04-04 20:23 ` redi at gcc dot gnu.org 2012-04-04 22:28 ` amodra at gmail dot com 2012-04-04 23:03 ` amodra at gmail dot com 2012-04-05 4:00 ` amodra at gmail dot com 2012-04-05 8:07 ` amodra at gmail dot com 2012-04-05 8:10 ` redi at gcc dot gnu.org 2012-04-05 12:05 ` amodra at gmail dot com 2012-04-05 13:03 ` redi at gcc dot gnu.org 2012-04-10 15:14 ` amodra at gmail dot com 2012-04-10 15:36 ` redi at gcc dot gnu.org 2012-04-10 15:59 ` redi at gcc dot gnu.org 2012-04-10 23:53 ` amodra at gmail dot com [this message] 2012-04-11 0:31 ` redi at gcc dot gnu.org 2012-04-11 0:59 ` redi at gcc dot gnu.org 2012-04-12 8:25 ` torvald at gcc dot gnu.org 2012-04-12 8:31 ` redi at gcc dot gnu.org 2012-04-12 9:19 ` amodra at gmail dot com 2012-04-12 10:06 ` redi at gcc dot gnu.org 2012-04-12 10:10 ` redi at gcc dot gnu.org 2012-04-13 20:52 ` [Bug libstdc++/52839] [4.7/4.8 Regression] " redi at gcc dot gnu.org 2012-04-14 13:25 ` amodra at gcc dot gnu.org 2012-04-21 13:30 ` amodra at gcc dot gnu.org 2012-04-21 13:35 ` amodra at gcc dot gnu.org 2012-04-21 13:38 ` amodra at gmail dot com 2012-11-02 1:36 ` pinskia at gcc dot gnu.org 2012-11-02 2:13 ` amodra at gmail dot com 2012-11-02 2:17 ` pinskia at gcc dot gnu.org 2012-11-02 2:39 ` amodra at gmail dot com 2012-11-02 2:41 ` pinskia at gcc dot gnu.org
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=bug-52839-4-u7QyGVB5Ba@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).