http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #13 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2013-04-17
20:41:54 UTC ---
> I can build successfully with either '--with-arch=i686 --build=mingw32' or
> '--build=i686-pc-mingw32', but as I mentioned in comment 10, change build
> target cause packaging issue.
Too bad, but I don't think this will ultimately change the decision, as
i686-pc-mingw32 is the standard triplet for Windows these days.
> What is the benefit to use '--build=i686-pc-mingw32' than '--with-arch=i686'?
It doesn't force -march=i686 by default.
