From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30245 invoked by alias); 10 Nov 2010 18:04:44 -0000 Received: (qmail 30234 invoked by uid 22791); 10 Nov 2010 18:04:44 -0000 X-SWARE-Spam-Status: No, hits=-2.8 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; Wed, 10 Nov 2010 18:04:40 +0000 From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/34940] contained subroutines called only once are not inlined 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: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC 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 Date: Wed, 10 Nov 2010 18:04:00 -0000 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-11/txt/msg01351.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34940 Jan Hubicka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus@net-b.de, hubicka at | |gcc dot gnu.org, kargl at | |gcc dot gnu.org --- Comment #6 from Jan Hubicka 2010-11-10 18:04:17 UTC --- Function is static, that seems OK. We inline it with ./xgcc -B ./ -O2 t.f90 -S --param large-stack-frame=2000 We are somewhat stupid here, since the call happens all the time and thus stack frame growth limits don't need to apply. I can implement this if this is common case for fortran. How commonly we run into these io structs? We can also bump large stack limits to make fortran I/O to fit in. Honza