From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11677 invoked by alias); 3 May 2012 00:14:17 -0000 Received: (qmail 11650 invoked by uid 22791); 3 May 2012 00:14:12 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 May 2012 00:14:00 +0000 From: "matz at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53197] [4.8 Regression] bootstrap comparison failure Date: Thu, 03 May 2012 00:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matz at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: matz at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-05/txt/msg00217.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53197 --- Comment #14 from Michael Matz 2012-05-03 00:13:16 UTC --- Thanks to Jonathan I have a hunch now. He has BUILD_CONFIG=bootstrap-debug whereas I have BUILD_CONFIG empty for all my machines. This means that for him stage2 is built with -g -gtoggle (effectively switching off -g again), and stage3 with -g, and the compares then do the comparison ignoring the debug info. For me stage2 and stage3 are built with -g. The -g switch seems to influence code generation with my patch (I tested that compiling the stage3 file on the broken tree with -gtoggle produces the same as the stage2 file), which of course is a bug. But I haven't seen it because all my files are built with -g. Now, as to why for me BUILD_CONFIG isn't bootstrap-debug: configure.ac activates this by default, but then checks if contrib/compare-debug actually works for comparing a debug and non-debug .o file. And for SuSE systems it doesn't, because our system compilers encode some command line options (among them -g) into a special .comment section. In any case, this code difference for -g vs. non-g has to be fixed, which I'm in the process of doing.