Allow different inlining cost factors for main/cold/frozen areas
commit9877851bb78998913a38d3a9e0448684b713bbeb
authorJan Oravec <[email protected]>
Thu, 20 Jun 2019 23:57:32 +0000 (20 16:57 -0700)
committerHhvm Bot <[email protected]>
Fri, 21 Jun 2019 00:05:14 +0000 (20 17:05 -0700)
tree37e5b29822e1f55db9d39531cbf235fa58ca217c
parent30b1e428e1b82e5fb4a9583947547fc5957afae0
Allow different inlining cost factors for main/cold/frozen areas

Summary:
When computing the cost of code for inlining purposes, it doesn't make sense to
count the hot code the same as the code that almost never executes. Let's have
a cost multiplier for each of the vasm areas.

This diff doesn't change the behavior yet, as all multipliers are currently set
to the same value. It allows experimentation via config updates.

Reviewed By: ricklavoie

Differential Revision: D15915891

fbshipit-source-id: 95d2922523c29bada1ad23f2bbf4190053b86c99
hphp/runtime/base/runtime-option.h
hphp/runtime/vm/jit/vasm-cost.cpp