public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kumba at gentoo dot 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 04:58:00 -0000 [thread overview]
Message-ID: <bug-61538-4-aa71aPkNI2@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 #8 from Joshua Kinard <kumba at gentoo dot org> ---
(In reply to Joshua Kinard from comment #7)
> (In reply to Andrew Pinski from comment #6)
> > This is the patch which I used for glibc to fix some libstdc++ issues:
>
> Okay, so it's in glibc. Is your patch in glibc yet? It applies cleanly to
> 2.19, but carries a 2012 date stamp. I'll rebuild and see if this solves
> the bug. Thanks!
Still hangs on the second syscall. I can trace the asm and see where it's
taking a different route due to those atomic_full_barrier() calls, but I'll
have to rebuild gcc next just to be completely sure.
next prev parent reply other threads:[~2014-06-19 4:58 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
2014-06-19 1:54 ` kumba at gentoo dot org
2014-06-19 4:58 ` kumba at gentoo dot org [this message]
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-aa71aPkNI2@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: 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).