https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113257
--- Comment #5 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
(In reply to Sam James from comment #3)
> (In reply to Richard Earnshaw from comment #2)
> I'm missing why the combination then works though?
So we've made several changes here over time.
-mcpu=native does attempt to find the core id to know what it is, but since
GCC-12 we also enable extensions that don't have a requirement on an
architecture.
So for instance on an SVE capable core we would enable it, but we of course
can't enable a tuning model.
But between GCC 13 and GCC 14 many things have changes. It looks like GCC-14
works as expected:
> ./install/bin/gcc -xc -S -o - - -march=native < /dev/null
.arch
armv8-a+flagm+dotprod+rdma+lse+crc+aes+sha3+fp16fml+rcpc+i8mm+bf16+sb+ssbs+pauth
.file "<stdin>"
.text
.ident "GCC: (GNU) 14.0.1 20240129 (experimental)"
.section
.note.GNU-stack,"",@progbits
> ./install/bin/gcc -xc -S -o - - -mcpu=native < /dev/null
.arch
armv8-a+flagm+dotprod+rdma+lse+crc+aes+sha3+fp16fml+rcpc+i8mm+bf16+sb+ssbs+pauth
.file "<stdin>"
.text
.ident "GCC: (GNU) 14.0.1 20240129 (experimental)"
.section
.note.GNU-stack,"",@progbits
> ./install/bin/gcc -xc -S -o - - -mcpu=native -march=native < /dev/null
.arch
armv8-a+flagm+dotprod+rdma+lse+crc+aes+sha3+fp16fml+rcpc+i8mm+bf16+sb+ssbs+pauth
.file "<stdin>"
.text
.ident "GCC: (GNU) 14.0.1 20240129 (experimental)"
.section
.note.GNU-stack,"",@progbits
So first question is, can you confirm it does for GCC-14 for you too?
In the meantime I'll try GCC-13
