From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9245 invoked by alias); 16 Feb 2015 06:41:25 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 9175 invoked by uid 48); 16 Feb 2015 06:41:19 -0000 From: "kumba at gentoo dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: regression X-Bugzilla-Version: 4.9.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: kumba at gentoo dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: version cf_known_to_fail bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-02/txt/msg01690.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61538 Joshua Kinard 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 --- 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.