CI arm64_darwin (gcc) still using c backend

[demoitem]

The title says it. It should be using the gcc backend as specified in the yml workflow but the logs tell a different story.
I'm guessing a concierge problem or one of the config files is overriding.

[VictorMiasnikov]

} one of the config

Files
m3-sys\m3cc\src\platforms.quake
and corresponded
m3makefile
don't contain any "ARM64_" entry.

But:
m3cc based on GCC 4.7.1 now

= =

GCC 4.7.1 supports the ARM architecture, including optimizations for ARM Cortex-A7 processors. But support for ARM64 (also called AArch64), the 64-bit version of ARM, came later, around GCC 4.8 or 4.9, and was improved in newer versions.

= =

[demoitem]

Right...
It appears that "concierge" checks if the gcc backend is available and, if not, uses the C backend. Isn't that an error?
A naive user thinks they have successfully built the compiler with the gcc backend, but in fact, they haven't.
I will remove the gcc backend for arm darwin. How do we specify the hardware on which we run the CI? We instruct it
to use macos but those old mac's used to run on intel chips didn't they? Hence amd64_darwin. Which still isn't working
and never will at 11.4. Maybe we need a new release.

[VictorMiasnikov]

( You have my e-mail address. If have questions then please write) As fact: first I solve "m3cc problem inside CI/CD" And Rodney Bates successfully implement method. In master branch method implemeted for AMD64_LINUX All theses branches have good CI/CD settings for AMD64_NT) } never will at 11.4 This never be a problem. Using "my branch" or latest release from master is the simplest way. Please use 5.11.4 inside CI/CD only for AMD64_NT and I386_NT  Even *_Mingw works good in CI/CD with  5.11.9

…

---------------- Кому: modula3/cm3 ***@***.***); Копия: Manual ***@***.***); Тема: [modula3/cm3] CI arm64_darwin (gcc) still using c backend (Issue #1216); 30.08.2025, 08:03, "peter mckinna" ***@***.***>: demoitem left a comment (modula3/cm3#1216) Right... It appears that "concierge" checks if the gcc backend is available and, if not, uses the C backend. Isn't that an error? A naive user thinks they have successfully built the compiler with the gcc backend, but in fact, they haven't. I will remove the gcc backend for arm darwin. How do we specify the hardware on which we run the CI? We instruct it to use macos but those old mac's used to run on intel chips didn't they? Hence amd64_darwin. Which still isn't working and never will at 11.4. Maybe we need a new release.