[v8-users] about v8's Machine code

I am wonder is that ignition shall save the native code it translated ? Or it just generate the code and then execute the code, save nothing. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscrib

Re: [v8-users] about v8's Machine code

Thanks, I get it. So now my problem is that the turbofan save the native code? I am not very clear about these two thing. On Monday, April 1, 2019 at 9:08:42 PM UTC+8, Jakob Kummerow wrote: > > Ignition does not produce executable machine code. It produces bytecode, > which is then interpreted.

Re: [v8-users] about v8's Machine code

Oh, thank you very much.Sometimes it would be a little difficult for me because I am not a native English man. That could be a really problem sometimes. On Tuesday, April 2, 2019 at 12:24:36 AM UTC+8, Jakob Kummerow wrote: > > Yes, Turbofan generates machine code, but that machine code is not >

[v8-users] About v8's closure( the [scope] )

I have a problem about v8's closure. The problem is that when the caller function finished, it's stack frame shall dismissed, then how could the callee function get access to the caller's context if the stack is not exist anymore ? Did we move those variable to the heap so that it could sti

Re: [v8-users] About v8's closure( the [scope] )

Oh, thanks. So it seems that I guess right. But in which moment we do that? Is that when the outer function finished or when we pre-parsing the function itself ? On Thursday, April 4, 2019 at 5:55:43 PM UTC+8, Jakob Kummerow wrote: > > Yes, a closure's "context" (i.e. variables from its outer s

Re: [v8-users] About v8's closure( the [scope] )

Wow, its cool! So it means those variables in the same function may not stored in the same place and we got those information before generate the byteCode right? On Friday, April 5, 2019 at 4:24:56 PM UTC+8, Jakob Kummerow wrote: > > After parsing we do scope analysis to decide where to allocat

Re: [v8-users] About v8's closure( the [scope] )

Oh, very thanks :). On Friday, April 5, 2019 at 5:02:11 PM UTC+8, Jakob Kummerow wrote: > > Correct. > > On Fri, Apr 5, 2019 at 10:56 AM > > wrote: > >> Wow, its cool! So it means those variables in the same function may not >> stored in the same place and we got those information before genera