[Bug other/64534] invalid -march value incosistency

[msebor at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64534

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-*, i?86-*-*
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2016-01-01
                 CC|                            |msebor at gcc dot gnu.org
               Host|                            |x86_64-*-*, i?86-*-*
     Ever confirmed|0                           |1
      Known to fail|                            |4.9.2, 5.1.0, 6.0

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed:

$ echo | /home/msebor/build/gcc-trunk-svn/gcc/xgcc
-B/home/msebor/build/gcc-trunk-svn/gcc -S -march=foobar -march=core2
-o/dev/null -xc -

$ echo | /home/msebor/build/gcc-trunk-svn/gcc/xgcc
-B/home/msebor/build/gcc-trunk-svn/gcc -S -march=foobar -march=native
-o/dev/null -xc -
<stdin>:1:0: error: bad value (foobar) for -march= switch

This seems to be due to the special treatment of -march=native by the i386
driver which forces it before any other -march= options, even if they are
specified first on the command line.