2009-03-17 H.J. Lu <hongjiu.lu@intel.com>

	PR target/39477
	* doc/extend.texi: Correct register behavior for regparm on
	Intel 386.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@144903 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6f50eb7..42240dc 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,11 @@
 2009-03-17  H.J. Lu  <hongjiu.lu@intel.com>
 
+       PR target/39477
+       * doc/extend.texi: Correct register behavior for regparm on
+       Intel 386.
+
+2009-03-17  H.J. Lu  <hongjiu.lu@intel.com>
+
        PR target/39476
        * config/i386/i386.c (ix86_function_regparm): Rewrite for
        64bit.

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 4739eaf..d335cde 100644 (file)
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2792,7 +2792,7 @@ default).  Lazy binding will send the first call via resolving code in
 the loader, which might assume EAX, EDX and ECX can be clobbered, as
 per the standard calling conventions.  Solaris 8 is affected by this.
 GNU systems with GLIBC 2.1 or higher, and FreeBSD, are believed to be
-safe since the loaders there save all registers.  (Lazy binding can be
+safe since the loaders there save EAX, EDX and ECX.  (Lazy binding can be
 disabled with the linker or the loader if desired, to avoid the
 problem.)