As stated in the PR, the docs claim that using -mtune without -march
will generate code that runs on i386, but that's not been true because
since GCC 4.5 the default -march is set by the configure target. This
patch updates the docs.
PR target/47643
* doc/invoke.texi (i386 and x86-64 Options): Fix description of
-mtune without -march.
OK for trunk?
Index: doc/invoke.texi
===================================================================
--- doc/invoke.texi (revision 182452)
+++ doc/invoke.texi (working copy)
@@ -12838,8 +12839,10 @@ Embedded AMD CPU with MMX and 3DNow!@: i
While picking a specific @var{cpu-type} will schedule things appropriately
for that particular chip, the compiler will not generate any code that
-does not run on the i386 without the @option{-march=@var{cpu-type}} option
-being used.
+does not run on the default machine type without the
@option{-march=@var{cpu-type}}
+option being used. For example, if GCC is configured for i686-pc-linux-gnu
+then @option{-mtune=pentium4} will generate code that is tuned for Pentium4
+but will still run on i686 machines.
@item -march=@var{cpu-type}
@opindex march
