https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104014
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Jakub Jelinek from comment #5) > That makes no sense. Surprising. bootstrap-O3 tests more of the compiler than the ordinary bootstrap-O2 does. That has to be a good thing for any candidate patch. > And, -march=native is a moving target, different for each developer. Indeed it is. We all have different boxes. But adding -march=native tests more of the compiler. > So bootstrap that works for one developer with -march=native can work fine > while on another box it will not. Agreed. But if a native bootstrap works for some machine, we can be pretty sure it will work for all predecessor machines of the same architecture. > --with-arch=native --with-cpu=native bootstraps aren't a good idea for > gcc-testresults posts as well because it is hard to determine what exactly > that native expands to. It wouldn't be impossible to require folks to specify what their native target was.
