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: Tue, 15 Jul 2014 07:38:00 -0000 [thread overview] Message-ID: <bug-61538-4-nEWgu9O2Hp@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 #15 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Joshua Kinard from comment #14) > (In reply to Andrew Pinski from comment #13) > > What is the kernel version? There has been some recent (this year) fixes > > inside the kernel for futex. > > > > Though I admit I have seen this just recently when debugging a program where > > I did next over a pthread_mutex_unlock call. > > Was under 3.14.x. I already tried going back to 3.14.0, due to the recent > futex security flaws covered in CVE-2014-3153. Now on 3.15.5 on the Octane, > and my test binaries still hang, so I've pretty much ruled out it being the > kernel. > > I've been doing a git bisect of gcc the last few days, and I've pinned the > problem commit down to somewhere between Jun 12 2012 and June 26 2012. > anything prior to the 26th works so far, anything after doesn't. My current > bisect build is going to test June 19 2012 next. Averages about ~7.5hrs for > gcc and 3.5hrs for glibc to build, so I can cram in roughly, 2 tests a day. I would try the daily date update right before 30c3c4427521f96fb58b6e1debb86da4f113f06f commit and then bispect from there because there are a few changes between the daily date update which could have caused this issue. > > So far, I am leaning towards commit 30c3c4427521f96fb58b6e1debb86da4f113f06f > as the culprit. That was added on June 20th, and I *think* the refactoring > of the case statement is wrong for MIPS. The logic just doesn't seem to > work out to be the same as the old code it replaced, and maybe this only is > a problem on the R10000 processors. I am also running into a similar issue (though not exactly the same) with a based GCC 4.7 toolchain with this change in too on Octeon. I am still trying to debug it and reproduce it.
next prev parent reply other threads:[~2014-07-15 7:38 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 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 [this message] 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-nEWgu9O2Hp@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).