From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E4E213832E5B; Thu, 27 Jun 2024 11:46:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E4E213832E5B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1719488772;
	bh=xI55Eca9CUzf9SvF5/PoFmmLdzhag6Y9eP45xWrLWmY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=L8vRpRt7TWtjMOewR9BvU0p4o16xL1bguxteKPb+RrR+55N5Hb0N9h8gu05t8QUJA
	 ONmsiurBvJVmFzYdHnNsz+5Q63hxYAju6B3yyGpRBHyq9Hy/rwIduvcnMIuw+xKGDw
	 iluRCtWveStMXGF3W1r8JOMZ07mzC1O+Fh+O8jf4=
From: "rvmallad at amazon dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/114531] Feature proposal for an
 `-finline-functions-aggressive` compiler option
Date: Thu, 27 Jun 2024 11:46: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: patch
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: <bug-114531-4-TQOiXchOe0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114531-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114531

--- Comment #19 from Rama Malladi <rvmallad at amazon dot com> ---
Thank you Hubicka@ for the inputs. I see your intent and that we have to
revisit the inline parameter tuning. As I and Richard S mentioned, the inte=
nt
of this feature request or PR is to expose such an option to the user for
getting aggressive inline optimizations enabled by the compiler.

Coming to some equivalent flags such as `-fvect-cost-model`, those flags al=
low
for choosing one of the multiple models such as 'dynamic', 'cheap'... In ca=
se
of inline parameter choice, we have only 2 choices: 'default', 'aggressive'.
Hence, adding an option such as `-finline-functions-aggressive` would be fi=
ne
to toggle between default and aggressive settings.=