From 3dd246d97b5a0b100597e046ed96a529395ebb95 Mon Sep 17 00:00:00 2001 From: redi Date: Thu, 22 Dec 2011 17:35:05 +0000 Subject: [PATCH 1/1] PR target/47643 * doc/invoke.texi (i386 and x86-64 Options): Fix description of -mtune without -march. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@182630 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 6 ++++++ gcc/doc/invoke.texi | 6 ++++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 3c785e1ce46..4788efa5c83 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2011-12-22 Jonathan Wakely + + PR target/47643 + * doc/invoke.texi (i386 and x86-64 Options): Fix description of + -mtune without -march. + 2011-12-21 Richard Earnshaw PR target/51643 diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 99427553edc..c779d27428f 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -12847,8 +12847,10 @@ Embedded AMD CPU with MMX and 3DNow!@: instruction set support. 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 -- 2.11.0