Re: [v8-users] Sample(process.cc) add code crash

2019-04-05 Thread helloev
full code: https://gitlab.com/snippets/1843803 On Friday, April 5, 2019 at 2:26:52 PM UTC+8, DaManuell wrote: > > Is there a crash is you suppress that global from your source? > > Le mardi 2 avril 2019 19:19:57 UTC+2, helloev a écrit : >> >> Global var >> >> On Tue, Apr 2, 2019 at 17:57 DaManuel

[v8-users] Re: v8 7.3.492-25 ARM gn Build with x86 gcc failed under linux x64

2019-04-05 Thread Roland E
Nevermind with: host_cpu="x64" target_cpu="arm" v8_target_cpu="arm" v8_use_snapshot=true v8_use_external_startup_data=true v8_enable_i18n_support=false v8_static_library=false is_component_build=true is_clang=false is_asan=false is_cfi=false clang_use_chrome_plugins=false treat_warning

[v8-users] v8 7.3.492-25 ARM gn Build with x86 gcc failed under linux x64

2019-04-05 Thread Roland E
Hi, I'm currently trying to build v8 armv7 binaries with my x64 ubuntu system and gcc. *v8 version: 7.3.492-25* v8 Buildsystem: gn OS Arch: x64 (Ubuntu 18.04.1 LTS 4.15.0-46-generic #49-Ubuntu SMP x86_64 GNU/Linux) gcc version: 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) *Environment vars:* target_ho

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

2019-04-05 Thread yangliang . 158556
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

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

2019-04-05 Thread Jakob Kummerow
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 generate the > byteCode right? > > On Friday, April 5, 2019 at 4:24:56 PM UTC+8, Jakob Kummerow wrote: >> >> A

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

2019-04-05 Thread yangliang . 158556
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] )

2019-04-05 Thread Jakob Kummerow
After parsing we do scope analysis to decide where to allocate each variable. Variables required by inner functions are allocated to the context. They are then directly written to and read from the context object whenever they are accessed. On Fri, Apr 5, 2019 at 9:03 AM wrote: > Oh, thanks. So

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

2019-04-05 Thread yangliang . 158556
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