This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Increase inline-unit-growth to 20%
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sat, 4 Apr 2015 23:09:38 +0200
- Subject: Increase inline-unit-growth to 20%
- Authentication-results: sourceware.org; auth=none
Hi,
as discussed in more detail at PR ipa/65655, decareasing unit growth to 15%
caused a regression in Firefox javascript benchmarks. While I was able to
fix most of it by badness metric improvement, about 7% gap remained,
so i am increasing growth to 20% (GCC 4.9 has 30%)
Honza
* invoke.texi (inline-unit-growth): Increase growth to 20%
* params.def (PARAM_INLINE_UNIT_GROWTH): Likewise.
Index: doc/invoke.texi
===================================================================
--- doc/invoke.texi (revision 221859)
+++ doc/invoke.texi (working copy)
@@ -10200,7 +10200,7 @@ before applying @option{--param inline-u
@item inline-unit-growth
Specifies maximal overall growth of the compilation unit caused by inlining.
-The default value is 15 which limits unit growth to 1.15 times the original
+The default value is 20 which limits unit growth to 1.2 times the original
size. Cold functions (either marked cold via an attribute or by profile
feedback) are not accounted into the unit size.
Index: params.def
===================================================================
--- params.def (revision 221859)
+++ params.def (working copy)
@@ -190,7 +190,7 @@ DEFPARAM(PARAM_LARGE_UNIT_INSNS,
DEFPARAM(PARAM_INLINE_UNIT_GROWTH,
"inline-unit-growth",
"How much can given compilation unit grow because of the inlining (in percent)",
- 15, 0, 0)
+ 20, 0, 0)
DEFPARAM(PARAM_IPCP_UNIT_GROWTH,
"ipcp-unit-growth",
"How much can given compilation unit grow because of the interprocedural constant propagation (in percent)",