On Fri, 18 Apr 2025, Martin Storsjö wrote:
> On Tue, 15 Apr 2025, Jeremy Drake via Mingw-w64-public wrote:
>
> > Unfortunately, the test-llvm-mingw and test-libcxx jobs fail for arm64.
> > I'm not clear on why. The test-ffmpeg jobs work, though
>
> FWIW, the tests that are failing aren't due to armv7 not being supported - it
> does seem to run just fine on the runners so far - they seem to run 10.0.22631
> aka 23H2. But at some point in the future I guess it no longer will be
> possible to run those binaries.
Correct
> And the test runner script assumes that when running via msys2 (which this
> does), it can run the built i686 and x86_64 executables, but nothing else. On
> these runners, we can run the outputs of all architectures, but we shouldn't
> try the really tricky ones when running emulated.
>
> This will need a little bit of tweaks in the llvm-mingw run-tests.sh script;
> I've got one way of fixing it done - once that's merged in llvm-mingw we can
> point the mingw-w64 CI to use that version.
You might have something more clever in mind, but technically everything
you need to know is in `uname` at this point (excluding things like WinPE
where not all binary types are present, and preview builds):
can_run_i686=true
can_run_x86_64=true
can_run_armv7=false
can_run_aarch64=false
if [[ "$(uname | cut -d- -f4)" = "ARM64" ]]; then
can_run_aarch64=true
winbuild="$(uname | cut -d- -f3)"
if [[ "$winbuild" -lt 22000 ]]; then
can_run_x86_64=false
fi
if [[ "$winbuild" -lt 26100 ]]; then
can_run_armv7=true
fi
elif [[ "$(uname -m)" = "i686" && "$(uname | cut -d- -f4)" != "WOW64" ]]; then
can_run_x86_64=false
fi
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
