Cirrus does not have arm64 vms for macOS yet from what I can see.
In theory we could work around this by making a fairly hacky docker container but that's unideal

I think it does:

https://cirrus-ci.org/guide/macOS/

It's probably new though.

Messing around with it here
https://github.com/clienthax/rpcs3/tree/arm64-tests

Bear in mind it should fail because of #12577

Also the arm building instructions from #12115 requires this change in hidapi:
sed -i '' "s/extern const double NSAppKitVersionNumber;/const double NSAppKitVersionNumber = 1343;/g" 3rdparty/hidapi/hidapi/mac/hid.c
Edit: Nevermind, this is already in the build script

Another known issue to be aware of is that it won’t build if qt@6 is installed. See #12477 ~

@clienthax I was having a look at your branch, and there are a few points about the build script I noticed.
(I was going to do a PR but I suddenly realised I don't know how Cirrus works, so I thought I'd just comment here)

When building for Arm on macOS there are a few CMake commands that are different than for x86:

-DPNG_ARM_NEON=ON <-- This is the Arm SIMD instruction set and should be on
-DCMAKE_OSX_ARCHITECTURES="arm64" <--This option is missing from the build script
-DLLVM_TARGETS_TO_BUILD="X86;AArch64;ARM" <-- I'm not sure why X86 is there, but it's on the Arm build instructions
-DUSE_SYSTEM_MVK=ON <-- I don't know if this is required when building on Cirrus
-DUSE_SYSTEM_FFMPEG=ON <-- Same

Just bumping this since Cirrus CI now builds the macOS artefacts using an Arm64 VM. It should be easier to implement now than before.

I wonder if arm64 compilation is possible now and if it is could a universal2 build be done

ill also look into building separately

For now it's best to just have arm64 separately in CI, universal2 build is not really interesting to spend time building on CI until the arm64 build works properly