juj
I am not using `--proxy-to-worker` anywhere.
> Can you explain more about this limitation? Is it worth fixing this maybe? When doing this, we parse `--js-library` on the command line in the order of presence. (I...
Currently we do already have ad hoc generated macros that did not get much design into them: - `{{{ from64('foo') }}}` which is like the proposed `{{{ ptrToIdx('foo') }}}`, but...
How to fix the lint errors? ``` C:\emsdk\emscripten\main>npm run lint --write ... 1:4384 error Strings must use singlequote quotes 1:4417 error Operator '=' must be spaced space-infix-ops 1:4418 error Strings...
> Seems reasonable if there is use case for it. Are there existing system library function that you had in mind when designing this attribute? I scanned library_browser.js and library_wasm_worker.js...
It looks like there is this wholesale proxy: 'sync' directive that is happening with the filesystem, so changed https://github.com/emscripten-core/emscripten/pull/22648/files#diff-5de5cdf403acefc1dc87b4446a186049adc104ceca678d993f3d5a007bcafcc5R273 to make tests pass. `fd_write` is also called in Wasm Workers.
I'll close this for later when I have time to split up the PR.
Indeed, these are fields that I missed in the initial implementation. Fortunately the options are passed as a struct, so it should be possible to expand to add these. I...
I don't know. To be precise, the issue doesn't occur on x64 Node.js 22.16.0. Only ARM64 version of Node.
The out of bounds access itself takes place on expression `*buffer` on the line `assert(*buffer == 42);`. Removing that avoids the issue.