From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31551 invoked by alias); 7 Dec 2004 17:50:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 31138 invoked by alias); 7 Dec 2004 17:50:10 -0000 Date: Tue, 07 Dec 2004 17:50:00 -0000 Message-ID: <20041207175010.31137.qmail@sourceware.org> From: "hubicka at ucw dot cz" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041128181553.18704.rguenth@tat.physik.uni-tuebingen.de> References: <20041128181553.18704.rguenth@tat.physik.uni-tuebingen.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/18704] [4.0 Regression] Inlining limits cause 340% performance regression X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg01027.txt.bz2 List-Id: ------- Additional Comments From hubicka at ucw dot cz 2004-12-07 17:50 ------- Subject: Re: [4.0 Regression] Inlining limits cause 340% performance regression > > ------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2004-12-07 15:35 ------- > Subject: Re: [4.0 Regression] Inlining limits > cause 340% performance regression > > On Tue, 7 Dec 2004, Richard Guenther wrote: > > > static inline void foo() {} > > void bar() { foo(); } > > > > which for -O2 -fprofile-generate produces > > > > bar: > > addl $1, .LPBX1 > > pushl %ebp > > movl %esp, %ebp > > adcl $0, .LPBX1+4 > > addl $1, .LPBX1+16 > > popl %ebp > > adcl $0, .LPBX1+20 > > addl $1, .LPBX1+8 > > adcl $0, .LPBX1+12 > > ret > > Mainline manages to produce > > bar: > addl $1, .LPBX1 > pushl %ebp > movl %esp, %ebp > adcl $0, .LPBX1+4 > popl %ebp > ret > > but that's RTL instrumentation? It is instrumentation after inlining. Before inlining you have two functions so you get two entry points. Doing little inlinng before profiling would do the trick here, but it needs some restructuring first. Honza > > > > -- > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18704 > > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18704