From: Jeff Law Date: Mon, 24 Nov 1997 20:52:10 +0000 (-0700) Subject: Doc fixes from Stan. X-Git-Tag: releases/egcs-1.0.0~71 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a0f3e78854aa199b72d4af7fb717e046cf30cdd;p=thirdparty%2Fgcc.git Doc fixes from Stan. From-SVN: r16690 --- diff --git a/gcc/invoke.texi b/gcc/invoke.texi index 7b65f6316e07..d3be572b7410 100644 --- a/gcc/invoke.texi +++ b/gcc/invoke.texi @@ -304,7 +304,9 @@ in the following sections. -mstats -EL -EB -G @var{num} -nocpp @emph{i386 Options} --m486 -m386 -mieee-fp -mno-fancy-math-387 +-mcpu=@var{cpu type} +-march=@var{cpu type} +-mieee-fp -mno-fancy-math-387 -mno-fp-ret-in-387 -msoft-float -msvr3-shlib -mno-wide-multiply -mrtd -malign-double -mreg-alloc=@var{list} -mregparm=@var{num} @@ -4456,11 +4458,27 @@ defaults. These @samp{-m} options are defined for the i386 family of computers: -@table @code -@item -m486 -@itemx -m386 -Control whether or not code is optimized for a 486 instead of an -386. Code generated for an 486 will run on a 386 and vice versa. +@item -mcpu=@var{cpu type} +Assume the defaults for the machine type @var{cpu type} when scheduling +instructions. The choices for @var{cpu type} are: @samp{i386}, +@samp{i486}, @samp{i586} (@samp{pentium}), @samp{pentium}, @samp{i686} +(@samp{pentiumpro}) and @samp{pentiumpro}. 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 @samp{-march=@var{cpu type}} option being used. + +@item -march=@var{cpu type} +Generate instructions for the machine type @var{cpu type}. The choices +for @var{cpu type} are: @samp{i386}, @samp{i486}, @samp{pentium}, and +@samp{pentiumpro}. Specifying @samp{-march=@var{cpu type}} implies +@samp{-mcpu=@var{cpu type}}. + +@item -m386 +@itemx -m486 +@itemx -mpentium +@itemx -mpentiumpro +Synonyms for -mcpu=i386, -mcpu=i486, -mcpu=pentium, and -mcpu=pentiumpro +respectively. @item -mieee-fp @itemx -mno-ieee-fp