* invoke.texi (-foptimize-sibling-calls): Fix.

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

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 5268b8f..30dd3f2 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+Thu Apr 27 15:08:46 MET DST 2000  Jan Hubicka  <jh@suse.cz>
+
+       * invoke.texi (-foptimize-sibling-calls): Fix.
+
 Thu Apr 27 14:54:22 MET DST 2000  Jan Hubicka  <jh@suse.cz>
 
        * loop.c (load_mems)  Don't use hard registers for the hoisting.

diff --git a/gcc/invoke.texi b/gcc/invoke.texi
index 67fd30b..d783205 100644 (file)
--- a/gcc/invoke.texi
+++ b/gcc/invoke.texi
@@ -2469,9 +2469,6 @@ restore frame pointers; it also makes an extra register available
 in many functions.  @strong{It also makes debugging impossible on
 some machines.}
 
-@item -foptimize-sibling-calls
-Optimize sibling and tail recursive calls.
-
 @ifset INTERNALS
 On some machines, such as the Vax, this flag has no effect, because
 the standard calling sequence automatically handles the frame pointer
@@ -2488,6 +2485,9 @@ whether a target machine supports this flag.  @xref{Registers,,Register
 Usage, gcc.info, Using and Porting GCC}.@refill
 @end ifclear
 
+@item -foptimize-sibling-calls
+Optimize sibling and tail recursive calls.
+
 @item -fno-inline
 Don't pay attention to the @code{inline} keyword.  Normally this option
 is used to keep the compiler from expanding any functions inline.