Simple inliner.
The Inlining phase.
A standard phase template
The global environment; overridden by instantiation in Global.
The global environment; overridden by instantiation in Global.
Names of phases that must run before this phase.
Names of phases that must run before this phase.
Name of the phase that this phase must follow immediately.
Name of the phase that this phase must follow immediately.
Maximum loop iterations.
The maximum size in basic blocks of methods considered for inlining.
Small method size (in blocks)
Is this component enabled? Default is true.
Is this component enabled? Default is true.
SubComponent are added to a HashSet and two phases are the same if they have the same name
SubComponent are added to a HashSet and two phases are the same if they have the same name
True if this phase runs before all other phases.
True if this phase runs before all other phases. Usually, parser.
True if this phase is not provided by a plug-in.
True if this phase is not provided by a plug-in.
Is the given class a closure?
Look up implementation of method 'sym in 'clazz'.
Create a new phase
Create a new phase
The phase corresponding to this subcomponent in the current compiler run
The phase corresponding to this subcomponent in the current compiler run
The name of the phase
The name of the phase
New flags defined by the phase which are not valid before
New flags defined by the phase which are not valid before
New flags defined by the phase which are not valid until immediately after it
New flags defined by the phase which are not valid until immediately after it
Names of phases required by this component.
Names of phases required by this component. Default is Nil.
Names of phases that must run after this phase.
Names of phases that must run after this phase. Default is Nil.
True if this phase runs after all other phases.
True if this phase runs after all other phases. Usually, terminal.
Inliner balances two competing goals: (a) aggressive inlining of: (a.1) the apply methods of anonymous closures, so that their anon-classes can be eliminated; (a.2) higher-order-methods defined in an external library, e.g.
Range.foreach()among many others. (b) circumventing the barrier to inter-library inlining that private accesses in the callee impose.Summing up the discussion in SI-5442 and SI-5891, the current implementation achieves to a large degree both goals above, and overcomes a problem exhibited by previous versions:
(1) Problem: Attempting to access a private member
pat runtime resulting in anIllegalAccessError, wherepis defined in a library L, and is accessed from a library C (for Client), where C was compiled against L', an optimized version of L where the inliner madeppublic at the bytecode level. The only such members are fields, either synthetic or isParamAccessor, and thus having a dollar sign in their name (the accesibility of methods and constructors isn't touched by the inliner).Thus we add one more goal to our list: (c) Compile C (either optimized or not) against any of L or L', so that it runs with either L or L' (in particular, compile against L' and run with L).
The chosen strategy is described in some detail in the comments for
accessRequirements()andpotentiallyPublicized(). Documentation at http://lamp.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/2011Q4/Inliner.pdf