Clara, There are 2 implementations of Escape Analysis in the optimizer:
- old_escape (escapeanalyzer.cpp) is an old prototype which does some analysis but does not actually optimize anything; - escape (escanalyzer.cpp) is a newer prototype which implements EA-based sychronization elimination and works on Windows/IA32. It showed a good performance improvement, but a new thread manager in DRLVM siginificantly reduced synchronization cost, so performance effect from escape pass became imperceptible and tjhe optimization has been turned off. You can try the 'escape' optimization pass by including it into the optimization path in the emconf file. For example, to add escape into the default optimizer path, edit your client.emconf as follows (added pass marked bold): -XDjit.CD_OPT.path.optimizer=ssa,devirt,inline,uce,purge,simplify,dce,uce,* escape*,lazyexc,memopt,simplify,dce,uce,lower,dessa,statprof,markglobals Thank you, Pavel On 12/15/06, clara <[EMAIL PROTECTED]> wrote:
Hi,all: I noticed that there were two kinds of escape analysis implementation in jitrino\src\optimizer. But what command options can be used to start these Escape Analysis? Thanks. -- Yu Zhang Univ. of Science & Technology of China(USTC)
