1. Optimizing J2ME applications with cross-module method inlining
Tarcisio P. Camara, et al.
Federal University of Pernambuco Center for Informatics, Brazil
Presented by Jiyong Park
Seoul National University, Korea

2. Summary Method inlining
Usually increases code size
Method inlining both increases performance and reduces code size
Makes use of JVM architecture and J2ME application model.
Provides decision algorithm for determining whether inlining or not.

3. Method Inlining with Temporary Vars
Variable binding mechanism

4. Method Inlining without Temporary Vars
Stack binding mechanism

5. Decision Algorithm

6. Decision Algorithm Parameter: MAX_EXPANSION Generates call graph
Calculate the size expansion due to the inlining at each call site.
If the cumulative expansion is less than the MAX_EXPANSION, to the inlining. If not, do not inline.
If all call sites of a method are inlined, then remove the method.

7. Decision Algorithm
Abstract, native, synchronized, constructor, methods that have catch exceptions are not inlined.
As a result,
Field access methods (Set/get)
Delegation methods
Methods called exactly at one site
are inlined.
They are about 50% of the reachable methods.

8. Results Size reduction: more than 3%
Performance improvement: up to 10%

9. Problems Serious problem with the presentation Bad English
Method inlining v.s. Cross-module method inlining
No appropriate explanation about the tables that show the results of the implementation.
I think this paper should be rejected.