https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100347
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2022-01-05
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
Going over the audit log it seems Iain cannot reproduce the observed failure of
-march=native, the only speciality the reporter mentions is that his build
system inserts a -march=skylake to each compiler command when building GCC (I
assume for stage1 only, and the reporter performs a bootstrap).
Erik, can you arrange for the compiler wrapper to not insert -march=skylake and
see whether that makes a difference? Otherwise as suggested you need to step
through the -march=native code, see comment#9
I've verified building (not bootstrapping) with --with-cpu= doesn't break
-march=native handling on x86_64-linux.
