On Dec 18, 2007 8:43 PM, 史成荣 <icyrong@gmail.com> wrote:
> why does it need setting the m2nframe before the slow path while it needn't
> when taking the fast path?
As I said below, that's for potential garbage collection or exception
throwing, when you need unwind the stack correctly.
Thanks,
xiaofeng
> 在07-12-18，Xiao-Feng Li <xiaofeng.li@gmail.com> 写道：
>
> >
> > Chengrong, locking is expensive, which should be optimized or avoided.
> > The fast path acquiring the lock without Java-native border crossing
> > can be much fast. It's expected the fast path be executed in most
> > cases. This is possible if the code sequence doesn't trigger garbage
> > collection or exception, hence no need to bookkeeping the frames.
> >
> > Thanks,
> > xiaofeng
> >
> >
>
--
http://xiao-feng.blogspot.com
|