https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #9 from Kip Warner ---
Yup. Agreed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #8 from Jakub Jelinek ---
Except for native supported on a subset of the architectures, no values are the
same, so this is highly target specific anyway. And yes, were it designed all
now, we'd use the same options, but some of these
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #7 from Kip Warner ---
I understand what you mean from a maintainer's standpoint. But from a user's
standpoint, that's an inconsistency.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #6 from Jakub Jelinek ---
There is no consistency.
Targets that have all of -march=, -mcpu= and -mtune=:
aarch64, arm, cris, i386 (-mcpu= deprecated and treated as -mtune=), m68k
Targets that have just -march= and -mtune=:
gcn, mips,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #5 from Kip Warner ---
The reason I asked is because of that inconsistency in the -mcpu usage on
targets. Thanks for clarifying.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
--- Comment #3 from Kip Warner ---
Martin, is -mcpu deprecated for all architectures or just x86?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97324
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #1 from Richard
