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 regression/61538] gcc after commit 39a8c5ea produces bad code for MIPS R1x000 CPUs Date: Mon, 16 Feb 2015 06:41:00 -0000 [thread overview] Message-ID: <bug-61538-4-of9G0kQboP@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 Joshua Kinard <kumba at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|4.8.0 |4.9.3 Known to fail| |4.9.3 Severity|major |critical --- Comment #23 from Joshua Kinard <kumba at gentoo dot org> --- Any chance someone from the MIPS side can take a look at this PR and figure out a solution? I cannot find a way to sanely-intercept the glibc build and get the preprocessed output of 'sln.c'. glibc's build system is just too complex to figure out. I reconfirmed the problem using gcc-4.9.3 20150119 (prerelease), by building it from the gcc-4_9-branch git branch, so this bug is still present. Still only seems to affect R10000, R12000, and R14000-based systems. Can easily reproduce on both an Octane (IP30) and Onyx2 (IP27). RM7000-based SGI O2 (IP32) does not seem to be affected, but I have not had that machine powered up lately to get a reverification.
next prev parent reply other threads:[~2015-02-16 6:41 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-17 17:31 [Bug c++/61538] New: g++ compiled binary, linked to glibc libpthread, hangs on SGI MIPS R1x000 systems on Linux 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 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 [this message] 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-of9G0kQboP@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).