From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9652 invoked by alias); 10 Oct 2009 15:17:47 -0000 Received: (qmail 9640 invoked by uid 22791); 10 Oct 2009 15:17:47 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 10 Oct 2009 15:17:41 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DC4C2109F9; Sat, 10 Oct 2009 15:19:14 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 2308F1086C; Sat, 10 Oct 2009 15:19:13 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MwdhR-00051r-Cw; Sat, 10 Oct 2009 11:17:37 -0400 Date: Sat, 10 Oct 2009 15:27:00 -0000 From: Daniel Jacobowitz To: Jan Hubicka Cc: Richard Guenther , Toon Moene , Jan Hubicka , gcc mailing list Subject: Re: LTO and the inlining of functions only called once. Message-ID: <20091010151737.GA18743@caradoc.them.org> Mail-Followup-To: Jan Hubicka , Richard Guenther , Toon Moene , Jan Hubicka , gcc mailing list References: <4AD0681E.5040200@moene.org> <84fc9c000910100400v5f1f4f35n5cd5c37c38c1420d@mail.gmail.com> <20091010123125.GO9046@atrey.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091010123125.GO9046@atrey.karlin.mff.cuni.cz> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-10/txt/msg00211.txt.bz2 On Sat, Oct 10, 2009 at 02:31:25PM +0200, Jan Hubicka wrote: > My solution would be probably to pass -fdump-ipa-inline parameter to lto > compilation and read the log. It lists the inlining decisions and if > something is not inlined, you get dump of reason why. GCC's dumps are really aimed at compiler developers. I think we would benefit from more "what is the compiler doing to my code" options (producing "note:"); things like which functions were inlined, which loops unrolled. We do already have this for vectorization. -- Daniel Jacobowitz CodeSourcery