> Commit 5be645a introduces the support of --with-cpu. The current > implementation specifies an `-march` option based on the default cpu > value. This behavior is not consistent with how the `-mcpu` option > works, however, as the `-mcpu` option involves both `-march` and > `-mtune`. Only setting the `-march` value can be confusing for users, > who may expect the --with-cpu option to act the same way as an explicit > `-mcpu` option. > > If it is some design choice, though, I would be glad to know.
We talked about this in the patchwork call today. To me this seems a reasonable change and I'd like to see this fixed sooner rather than later, but, again, I guess it's no regression but just unfortunate. So we probably need to defer to 17. IMHO we should backport this to GCC 16 after the release, though. -- Regards Robin
