Update.

1999-08-18  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* manual/install.texi (Configuring and compiling): Clarify ix86
	situation.

3 files changed, 25 insertions, 23 deletions

diff --git a/ChangeLog b/ChangeLog
index 461e3bb822..4a2302729f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+1999-08-18  Andreas Jaeger  <aj@arthur.rhein-neckar.de>
+
+	* manual/install.texi (Configuring and compiling): Clarify ix86
+	situation.
+
 1999-08-18  Ulrich Drepper  <drepper@cygnus.com>
 
 	* Rules: When generating stdio_lim.h also rewrite IOV_MAX definition.
diff --git a/INSTALL b/INSTALL
index 6b2928bc99..8d66e8c37d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -145,11 +145,10 @@ will be used, and CFLAGS sets optimization options for the compiler.
      compile but use what you say instead of guessing what your system
      is.  This is most useful to change the CPU submodel.  For example,
      if configure guesses your machine as `i586-pc-linux-gnu' but you
-     want to compile a library optimized for 386es, give
+     want to compile a library for 386es, give
      `--host=i386-pc-linux-gnu' or just `--host=i386-linux' and add the
      appropriate compiler flags (`-mcpu=i386' will do the trick) to
-     CFLAGS. (A library compiled for a Pentium (`i586') will still work
-     on a 386, but it may be slower.)
+     CFLAGS.
 
      If you give just `--build', configure will get confused.
 
@@ -370,13 +369,13 @@ If you are interested in doing a port, please contact the glibc
 maintainers by sending electronic mail to <bug-glibc@gnu.org>.
 
    Each case of `iX86' can be `i386', `i486', `i586', or `i686'.  All
-of those configurations produce a library that can run on any of these
-processors if the compiler is configured correctly.  The GCC compiler
-by default generates code that's optimized for the machine it's
-configured for and will use the instructions available on that machine.
-For example if your GCC is configured for `i686', gcc will optimize
-for `i686' and might issue some `i686' specific instructions.  To
-generate code for other models you should give GCC the appropriate
+of those configurations produce a library that can run on this
+processor and newer processors.  The GCC compiler by default generates
+code that's optimized for the machine it's configured for and will use
+the instructions available on that machine.  For example if your GCC is
+configured for `i686', gcc will optimize for `i686' and might issue
+some `i686' specific instructions.  To generate code for other models,
+you have to configure for that model and give GCC the appropriate
 `-march=' and `-mcpu=' compiler switches via CFLAGS.
 
 Specific advice for Linux systems
diff --git a/manual/install.texi b/manual/install.texi
index 60a5edefdf..2905b05625 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -170,11 +170,9 @@ If you give just @samp{--host}, configure will prepare for a native
 compile but use what you say instead of guessing what your system is.
 This is most useful to change the CPU submodel.  For example, if
 configure guesses your machine as @code{i586-pc-linux-gnu} but you want
-to compile a library optimized for 386es, give
-@samp{--host=i386-pc-linux-gnu} or just @samp{--host=i386-linux} and add
-the appropriate compiler flags (@samp{-mcpu=i386} will do the trick) to
-@var{CFLAGS}. (A library compiled for a Pentium (@code{i586}) will still
-work on a 386, but it may be slower.)
+to compile a library for 386es, give @samp{--host=i386-pc-linux-gnu} or
+just @samp{--host=i386-linux} and add the appropriate compiler flags
+(@samp{-mcpu=i386} will do the trick) to @var{CFLAGS}.
 
 If you give just @samp{--build}, configure will get confused.
 @end table
@@ -422,14 +420,14 @@ maintainers by sending electronic mail to @email{bug-glibc@@gnu.org}.
 
 Each case of @samp{i@var{x}86} can be @samp{i386}, @samp{i486},
 @samp{i586}, or @samp{i686}.  All of those configurations produce a
-library that can run on any of these processors if the compiler is
-configured correctly.  The GCC compiler by default generates code
-that's optimized for the machine it's configured for and will use the
-instructions available on that machine.  For example if your GCC is
-configured for @samp{i686}, gcc will optimize for @samp{i686} and
-might issue some @samp{i686} specific instructions.  To generate code
-for other models you should give GCC the appropriate @samp{-march=}
-and @samp{-mcpu=} compiler switches via @var{CFLAGS}.
+library that can run on this processor and newer processors.  The GCC
+compiler by default generates code that's optimized for the machine it's
+configured for and will use the instructions available on that machine.
+For example if your GCC is configured for @samp{i686}, gcc will optimize
+for @samp{i686} and might issue some @samp{i686} specific instructions.
+To generate code for other models, you have to configure for that model
+and give GCC the appropriate @samp{-march=} and @samp{-mcpu=} compiler
+switches via @var{CFLAGS}.
 
 @node Linux
 @appendixsec Specific advice for Linux systems