From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7A5233870886; Tue, 25 Jun 2024 15:30:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7A5233870886 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1719329412; bh=p17o/36fYjWd8L/LKstJ5iRCP2mHimm1hGY/DHtAf3I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ecm9JlT+lEYoRSVA+NHV4vJKYf+dyXpiwtwlVHmciI5jCL2PW2mc/s7L5nLrCJE75 ONNvqDL4ErWseDKJRRY+s5dAxzb2iyzvsRXmTwZeOGyy30RCExWKD5/4ODtzjVnktY fBXoBYv+nZQ6VxBNCBzK37Nf8Dnwxn4sUoU0pJdI= From: "rvmallad at amazon dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114531] Feature proposal for an `-finline-functions-aggressive` compiler option Date: Tue, 25 Jun 2024 15:30:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: rvmallad at amazon dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114531 --- Comment #11 from Rama Malladi --- (In reply to Wilco from comment #10) > A 1.1% overall performance gain looks good - is there a significant codes= ize > hit from this? If so, are there slightly less aggressive settings that st= ill > get most of the performance gains but at a lower (acceptable) codesize co= st? > It seems there may be scope to improve the default settings of -O2. Here is a code size comparison of O2 vs. O2 + inline params for SPEC cpu2017 Int Rate benchmarks. One of the concerns for not modifying the default inli= ne parameters at -O2 is loss of some function observability due to aggressive inline optimizations. Benchmark "-O2" "-O2 + inline size params" increase 500.perlbench_r 8.5M 11M 1.29 502.gcc_r 51M 56M 1.10 505.mcf_r 102K 106K 1.04 520.omnetpp_r 22M 23M 1.05 523.xalancbmk_r 52M 53M 1.02 525.x264_r 2.5M 2.8M 1.12 531.deepsjeng_r 416K 441K 1.06 541.leela_r 2.6M 2.6M 1.00 548.exchange2_r 115K 115K 1.00 557.xz_r 818K 871K 1.06 999.specrand_ir 24K 24K 1.00=