This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Cleanup i386 documentation in invoke.texi
- To: gcc-patches at gcc dot gnu dot org
- Subject: Cleanup i386 documentation in invoke.texi
- From: Andreas Jaeger <aj at suse dot de>
- Date: Wed, 05 Sep 2001 09:50:28 +0200
Looking through the i386 options, I noticed some problems and fixed
them.
Ok for both branches?
The patch passes make dvi and make info.
Andreas
2001-09-05 Andreas Jaeger <aj@suse.de>
* doc/invoke.texi (i386 Options): -mwide-multiply is not
available anymore, remove the documentation.
(i386 Options): Fix typo, cleanup index entries.
============================================================
Index: gcc/doc/invoke.texi
--- gcc/doc/invoke.texi 2001/09/04 12:12:50 1.50
+++ gcc/doc/invoke.texi 2001/09/05 07:45:27
@@ -7494,9 +7494,7 @@ produce code that runs somewhat faster o
expense of more memory.
@item -m128bit-long-double
-@itemx -m128bit-long-double
@opindex m128bit-long-double
-@opindex m128bit-long-double
Control the size of @code{long double} type. i386 application binary interface
specify the size to be 12 bytes, while modern architectures (Pentium and newer)
prefer @code{long double} aligned to 8 or 16 byte boundary. This is
@@ -7508,8 +7506,6 @@ well as function calling convention for
will be modified.
@item -m96bit-long-double
-@itemx -m96bit-long-double
-@opindex m96bit-long-double
@opindex m96bit-long-double
Set the size of @code{long double} to 96 bits as required by the i386
application binary interface. This is the default.
@@ -7522,14 +7518,6 @@ Control whether GCC places uninitialized
@code{bss} or @code{data} segments. @option{-msvr3-shlib} places them
into @code{bss}. These options are meaningful only on System V Release 3.
-@item -mno-wide-multiply
-@itemx -mwide-multiply
-@opindex mno-wide-multiply
-@opindex mwide-multiply
-Control whether GCC uses the @code{mul} and @code{imul} that produce
-64-bit results in @code{eax:edx} from 32-bit operands to do @code{long
-long} multiplies and 32-bit division by constants.
-
@item -mrtd
@opindex mrtd
Use a different function-calling convention, in which functions that
@@ -7596,7 +7584,9 @@ may want to reduce the preferred alignme
@option{-mpreferred-stack-boundary=2}.
@item -mpush-args
+@itemx -mno-push-args
@opindex mpush-args
+@opindex mno-push-args
Use PUSH operations to store outgoing parameters. This method is shorter
and usually equally fast as method using SUB/MOV operations and is enabled
by default. In some cases disabling it may improve performance because of
@@ -7605,7 +7595,7 @@ improved scheduling and reduced dependen
@item -maccumulate-outgoing-args
@opindex maccumulate-outgoing-args
If enabled, the maximum amount of space required for outgoing arguments will be
-computed in the function prologue. This in faster on most modern CPUs
+computed in the function prologue. This is faster on most modern CPUs
because of reduced dependencies, improved scheduling and reduced stack usage
when preferred stack boundary is not equal to 2. The drawback is a notable
increase in code size. This switch implies @option{-mno-push-args}.
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj