From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15206 invoked by alias); 7 Feb 2002 11:48:55 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15016 invoked from network); 7 Feb 2002 11:48:45 -0000 Received: from unknown (HELO atrey.karlin.mff.cuni.cz) (195.113.31.123) by sources.redhat.com with SMTP; 7 Feb 2002 11:48:45 -0000 Received: (from hubicka@localhost) by atrey.karlin.mff.cuni.cz (8.9.3/8.9.3/Debian 8.9.3-21) id MAA01137; Thu, 7 Feb 2002 12:48:36 +0100 Date: Thu, 07 Feb 2002 03:59:00 -0000 From: Jan Hubicka To: Andreas Jaeger Cc: Dale Johannesen , Laurent Guerby , Paolo Carlini , gcc@gcc.gnu.org, rth@redhat.com Subject: Re: Loop unrolling-related SPEC regressions? Message-ID: <20020207114836.GI26252@atrey.karlin.mff.cuni.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.24i X-SW-Source: 2002-02/txt/msg00519.txt.bz2 > Dale Johannesen writes: > > > Intelligent use of profiling info from the first pass is > > important. You'll see the published numbers do this. > > Last time I looked gcc used this only for branch > > straightening; it can also be used effectively to > > drive inlining and register allocation. > > AFAIK the infrastructure is there, it only needs to be used for > inlining - and also in the new register allocator. Michal, is this > possible? It is not possible to use it for inlining yet, as our loop optimization pass kill profile info, so unless we want to have multiple passes needed for optimization, we need to rewrite that one as well as RTL code generation first. We are working on that. It is already used for register allocation in the mainline as well as for few of other decision. CFG branch is more aggressive already deriving about 5% benefit. I hope this to improve as the code matures. Honza