Thanks, that makes sense. If the write towards lower address page by page, it looks similar to _chkstk. BTW: any hint on which part of V8 code handles this, like generating these writes?
On Thursday, October 4, 2018 at 11:32:41 AM UTC-7, Yang Guo wrote: > > iirc we simply write to these stack locations to make sure they are > committed. > > Yang > > On Thu, Oct 4, 2018 at 8:21 PM <[email protected] <javascript:>> wrote: > >> Large stack allocation on Windows usually needs to call _chkstk to make >> sure the the memory is committed. C++ function should be handled by C++ >> compiler automatically, but I didn't see any call to _chkstk() in V8 source >> for JIT code. Is it handled in some different way? >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> http://groups.google.com/group/v8-dev >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
