From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14963 invoked by alias); 12 Jul 2010 23:45:15 -0000 Received: (qmail 14837 invoked by uid 48); 12 Jul 2010 23:45:03 -0000 Date: Mon, 12 Jul 2010 23:45:00 -0000 Message-ID: <20100712234503.14836.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/44921] [4.6 Regression] Failed to bootstrap In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "amylaar at gcc dot gnu dot org" 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: 2010-07/txt/msg01331.txt.bz2 ------- Comment #5 from amylaar at gcc dot gnu dot org 2010-07-12 23:45 ------- (In reply to comment #3) > Does the first chunk count as obvious? I'd say yes. My boostraps using that hunk with and without --enable-build-with-cxx on i686-pc-linux-gnu have progressed past the stage2/stage3 comparison. (In reply to comment #4) > int min_regno = 0; > > is faster. Yes, it's a cheaper constant on a number of processors in term of size and speed. If we really care about compiler run-time efficiency here (and efficiency for programs that use the same warning regime), we should introduce an attribute to tell the compiler to treat a variable as initialized even if it isn't, so that attribute can be used in these cases of the variable always being assigned before used even if no proof exists inside the rule system of the compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44921