https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110901
--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Tamar Christina <tnfch...@gcc.gnu.org>: https://gcc.gnu.org/g:f8daec2ad9a20c31a98efb4602080e1e5d0c19fe commit r14-11255-gf8daec2ad9a20c31a98efb4602080e1e5d0c19fe Author: Tamar Christina <tamar.christ...@arm.com> Date: Thu Jan 16 19:23:50 2025 +0000 AArch64: don't override march to assembler with mcpu if march is specified [PR110901] When both -mcpu and -march are specified, the value of -march wins out. This is done correctly for the calls to cc1 and for the assembler directives we put out in assembly files. However in the call to as we don't do this and instead use the arch from the cpu. This leads to a situation that GCC cannot reliably be used to compile assembly files which don't have a .arch directive. This is quite common with .S files which use macros to selectively enable codepath based on what the preprocessor sees. The fix is to change MCPU_TO_MARCH_SPEC to not override the march if an march is already specified. gcc/ChangeLog: PR target/110901 * config/aarch64/aarch64.h (MCPU_TO_MARCH_SPEC): Don't override if march is set. gcc/testsuite/ChangeLog: PR target/110901 * gcc.target/aarch64/options_set_29.c: New test. (cherry picked from commit 773beeaafb0ea31bd4e308b64781731d64b571ce)
