From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29141 invoked by alias); 11 Sep 2011 09:42:51 -0000 Received: (qmail 29116 invoked by uid 22791); 11 Sep 2011 09:42:50 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 11 Sep 2011 09:42:37 +0000 From: "hubicka at ucw dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49997] [4.7 Regression] ICE in inline_small_functions with -fnon-call-exceptions Date: Sun, 11 Sep 2011 10:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at ucw dot cz X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2011-09/txt/msg00748.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49997 --- Comment #5 from Jan Hubicka 2011-09-11 09:42:32 UTC --- > Possibly. Last time I tried it it however lead to bigger and slower binaries. > Well, I will patch frescobaldi today and lets see. OK, removing this trick alone regress tramp3d by about 80%,and capacita by about 15%. Causes small regression on wave & nbench. reduces size a bit for dlv. The reason for this is to drive heuristic to preffer functions that can ultimately be fully inlined wihtout much of effort. Frankly I think this makes sense. We could of course reach this otherwise. Like compute expected growths just once and expect that other inlining won't affect them in important way (that si wrong of course) and/or just cut the update algorithm by fixed threshold allowing priority queue to ba partly out of date when we run into the most expensive cases. Honza