From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32167 invoked by alias); 3 Apr 2010 21:21:39 -0000 Received: (qmail 30647 invoked by alias); 3 Apr 2010 21:21:14 -0000 Date: Sat, 03 Apr 2010 21:21:00 -0000 Message-ID: <20100403212114.30646.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/40436] [4.5 regression] 0.5% code size regression caused by r147852 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hubicka at ucw dot cz" 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-04/txt/msg00311.txt.bz2 ------- Comment #26 from hubicka at ucw dot cz 2010-04-03 21:20 ------- Subject: Re: [4.5 regression] 0.5% code size regression caused by r147852 As for history, I oriignally had only the perentage limits at place, but then found that they behave really erratically on small units and small functions. (especially in kernel source where you have tiny units with two functions that needs to be inlined one to other). So I added this large function/unit thresholds. They should be symmetric for functions and units. Honza -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40436