The Acorn optimizer runs on code that is combined with the Emscripten JS
output. That is the main JS output, including JS library support, and also
--pre/post-js and EM_ASM code, which are combined and then optimized as one
(which is good for DCE).
On Tue, Apr 2, 2024 at 8:38 AM 'Michael Hagar'
Does the acorn optimizer only run on Emscripten generated JS? In my case,
I'm accessing Module.HEAPU8 directly from my own JS (which is not library
JS). Based on the documentation
here:
https://emscripten.org/docs/porting/pthreads.html?highlight=growable#special-considerations
If I am using
Thanks! I haven't tested using the non-GROWABLE methods for heap access,
but that's good to know they shouldn't be needed.
On Friday, July 7, 2023 at 7:41:51 PM UTC-5 s...@google.com wrote:
> Yes, those methods are only used/needed/present when growable memory is
> combined with threads.
>
>
Yes, those methods are only used/needed/present when growable memory is
combined with threads.
What is more, you should not normally need to use them directly since
emscripten should automatically convert all your heap accesses. This is
done using the `growableHeap` in
Do I need to use the GROWABLE_HEAP_X methods if I am only using
ALLOW_MEMORY_GROWTH, but not pthreads?
--
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
