Feature idea
Apple completed its transition to ARM-based processors in new devices a few years ago; however, the ASPL toolchain still only officially supports x86_64 for macOS (see "Additional context" for what "officially" means here).
Possible solutions/implementations
Add full support for ARM64 macOS just like any other target.
Alternatives considered
No response
Additional context
In principle, ASPL, that is to say the language itself as well as the compiler and the standard library, is mostly architecture independent, as the C stdlib and the C compiler do most of the heavy lifting in both the C and the AIL backend. However, the CI/CD pipeline, the installer, and the CLI tool only consider a handful of common architectures and operating systems, which currently do not (fully) include ARM macOS. Thus, compiling ASPL software, including the ASPL compiler, for this target currently requires some manual setup, and the CI does not test anything there yet. As laid out above, it is about time for this to change, which should hopefully not be a lot of work anyway.
Contributing guidelines
Feature idea
Apple completed its transition to ARM-based processors in new devices a few years ago; however, the ASPL toolchain still only officially supports x86_64 for macOS (see "Additional context" for what "officially" means here).
Possible solutions/implementations
Add full support for ARM64 macOS just like any other target.
Alternatives considered
No response
Additional context
In principle, ASPL, that is to say the language itself as well as the compiler and the standard library, is mostly architecture independent, as the C stdlib and the C compiler do most of the heavy lifting in both the C and the AIL backend. However, the CI/CD pipeline, the installer, and the CLI tool only consider a handful of common architectures and operating systems, which currently do not (fully) include ARM macOS. Thus, compiling ASPL software, including the ASPL compiler, for this target currently requires some manual setup, and the CI does not test anything there yet. As laid out above, it is about time for this to change, which should hopefully not be a lot of work anyway.
Contributing guidelines