public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61538] g++ compiled binary, linked to glibc libpthread, hangs on SGI MIPS R1x000 systems on Linux Date: Thu, 19 Jun 2014 01:11:00 -0000 [thread overview] Message-ID: <bug-61538-4-oOYmCqS4gn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61538-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This is the patch which I used for glibc to fix some libstdc++ issues: >From 2788414e4e6a548766aa7e732fc096f9f572302e Mon Sep 17 00:00:00 2001 From: Andrew Pinski <apinski@cavium.com> Date: Thu, 1 Nov 2012 23:07:22 -0700 Subject: [PATCH] 2012-11-01 Andrew Pinski <apinski@cavium.com> Bug #5086 * ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c (__pthread_once): Add release barrier before setting once_control to say initialisation is done. (clear_once_control): Add release barrier. --- ChangeLog.CAVIUM | 8 ++++++++ .../unix/sysv/linux/mips/nptl/pthread_once.c | 2 ++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/ChangeLog.CAVIUM b/ChangeLog.CAVIUM index 8ed42ea..5975430 100644 --- a/ChangeLog.CAVIUM +++ b/ChangeLog.CAVIUM @@ -1,3 +1,11 @@ +2012-11-01 Andrew Pinski <apinski@cavium.com> + + Bug #5086 + * ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c (__pthread_once): + Add release barrier before setting once_control to say + initialisation is done. + (clear_once_control): Add release barrier. + 2012-10-28 Andrew Pinski <apinski@cavium.com> Bug #5059 diff --git a/ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c b/ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c index 308da8b..c2ef264 100644 --- a/ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c +++ b/ports/sysdeps/unix/sysv/linux/mips/nptl/pthread_once.c @@ -28,6 +28,7 @@ clear_once_control (void *arg) { pthread_once_t *once_control = (pthread_once_t *) arg; + atomic_full_barrier (); *once_control = 0; lll_futex_wake (once_control, INT_MAX, LLL_PRIVATE); } @@ -80,6 +81,7 @@ __pthread_once (once_control, init_routine) /* Add one to *once_control. */ + atomic_full_barrier (); atomic_increment (once_control); /* Wake up all other threads. */ -- 1.7.4.1
next prev parent reply other threads:[~2014-06-19 1:11 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-17 17:31 [Bug c++/61538] New: " kumba at gentoo dot org 2014-06-17 18:07 ` [Bug c++/61538] " kumba at gentoo dot org 2014-06-18 16:55 ` redi at gcc dot gnu.org 2014-06-18 22:06 ` kumba at gentoo dot org 2014-06-19 1:11 ` pinskia at gcc dot gnu.org [this message] 2014-06-19 1:54 ` kumba at gentoo dot org 2014-06-19 4:58 ` kumba at gentoo dot org 2014-06-21 1:21 ` kumba at gentoo dot org 2014-06-21 1:59 ` kumba at gentoo dot org 2014-07-06 20:29 ` kumba at gentoo dot org 2014-07-15 5:02 ` pinskia at gcc dot gnu.org 2014-07-15 6:42 ` kumba at gentoo dot org 2014-07-15 7:38 ` pinskia at gcc dot gnu.org 2014-07-21 7:00 ` kumba at gentoo dot org 2014-07-21 7:10 ` [Bug regression/61538] gcc after commit 39a8c5ea produces bad code for MIPS R1x000 CPUs kumba at gentoo dot org 2014-07-21 7:17 ` kumba at gentoo dot org 2014-10-21 6:04 ` pinskia at gcc dot gnu.org 2014-10-21 6:30 ` kumba at gentoo dot org 2015-02-16 6:41 ` kumba at gentoo dot org 2015-02-18 8:22 ` kumba at gentoo dot org 2015-02-18 9:24 ` 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-61538-4-oOYmCqS4gn@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).