Both of those flags affect how s2wasm's linker lays out the linear memory
space. Globals (the users's static data) go at the very bottom starting at
address 0, but you can leave some space underneath them by setting
--global-base to something larger than 0. This includes the stack pointer.
If you use --allocate-stack, the linker will also allocate space for the
stack itself. It goes after the users' static data, and has the size that
you specify to --allocate-stack.
On Thu, Aug 24, 2017 at 9:54 PM Jean Valjean <me...@hotmail.com> wrote:
> Hey there,
>
> I guess my question is pretty straight but: For s2wasm, what distinguishes
> --global-base from --allocate-stack ?
>
> I don't really understand the purpose of --allocate-stack (wasm has its
> own way to allocate variable on the stack with «set_local») and I guess
> it's something related to --global-base.
>
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to emscripten-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
