Evgeny Karpov
Evgeny Karpov
It looks it can be reproduced on our side. Thanks for reporting this.
The issue is not reproducible anymore in this repo. https://github.com/eukarpov/gnu-toolchain-windows-arm64
> > Ideally I think the code would avoid generating temp JS objects. > > Good point, +1 Let's avoid the object creation here. For now the code has been...
> By object creation, we mean the line with `const arrayClasses = { .. }`. That allocates a new object each time it is reached (maybe not each loop iteration...
The issue is no longer reproducible. Most likely, it was related to the runtime relocation issue in mingw when shared runtime libraries are linked and that has been fixed. https://github.com/Windows-on-ARM-Experiments/mingw-woarm64/pull/9
Bash build has been added to CI and all required workarounds have been merged to bash and cygwin repos. https://github.com/Windows-on-ARM-Experiments/mingw-woarm64-build/pull/309 https://github.com/Windows-on-ARM-Experiments/bash/pull/1 https://github.com/Windows-on-ARM-Experiments/newlib-cygwin/pull/16
It looks like a case when C++ is used in configuration. It is not supported yet. However it is coming soon. Most probably with patch series 3 or 4.
The issue will be fixed in the patch series 3 by enabling minimal C++ support in the toolchain.
The issue should be resolved after upstreaming this patch series. https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668484.html
It looks like a case when C++ is used in configuration. It is not supported yet. However it is coming soon. Most probably with patch series 3 or 4.