backport: re PR target/39477 (Incorrect document for regparm attribute)

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

	Backport from mainline:
	2009-03-17  H.J. Lu  <hongjiu.lu@intel.com>

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

From-SVN: r144904

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 7ebb4f2155f36f3adca0cdacd745a68d755b3c7a..f756219bcc0296ecba749e12c297ebd3ec24030a 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2009-03-17  H.J. Lu  <hongjiu.lu@intel.com>
+
+       Backport from mainline:
+       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-12  H.J. Lu  <hongjiu.lu@intel.com>
 
        Backport from mainline:

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 721867b5d4b3cea4f40547d385feb9c9cbe8d22a..61376ce3026a828113d12142b9ede46b2887e621 100644 (file)
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2687,7 +2687,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.)