[Bug target/113625] Interesting behavior with and without -mcpu=generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113625 Tamar Christina changed: What|Removed |Added CC||tnfchris at gcc dot gnu.org --- Comment #4 from Tamar Christina --- Generic is not the default for aarch64 and the default depends on the architecture revision. The documentation patch got stuck on bike shedding on the list. I'll resubmit it tomorrow. Generic was kept around for backwards compatibility reasons. That said, both codegen below are suboptimal...
[Bug target/113625] Interesting behavior with and without -mcpu=generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113625 --- Comment #3 from Andrew Pinski --- I should note that gcc.target/aarch64 tests are explicitly tested with -mtune=generic ...
[Bug target/113625] Interesting behavior with and without -mcpu=generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113625 --- Comment #2 from Andrew Pinski --- Just FYI this is how I configured GCC: ``` Configured with: ../configure --target=aarch64-linux-gnu --prefix=/home/apinski/src/upstream-full-cross/install --enable-languages=c,c++,fortran,go --with-sysroot=/home/apinski/src/upstream-full-cross/install//sysroot ``` Nothing special even.
[Bug target/113625] Interesting behavior with and without -mcpu=generic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113625 --- Comment #1 from Richard Biener --- Other targets (x86_64) default to -mtune=generic. Maybe configure time selection somehow interferes with this on aarch64?