Delete obsolete doc pointed out by Chris Lattner.

* doc/interface.texi (longjmp and automatic variables): Delete
paragraph recommending taking the address of a variable.

From-SVN: r84160

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 9c65170f8bc743b7c5b37e62e888c5a3ef479826..9f2d1c1bc56b3f3ff6c293eb17a09caa7bdaab22 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2004-07-06  James E Wilson  <wilson@specifixinc.com>
+
+       * doc/interface.texi (longjmp and automatic variables): Delete
+       paragraph recommending taking the address of a variable.
+
 2004-07-06  Nathan Sidwell  <nathan@codesourcery.com>
 
        * vec.h (VEC_embedded_alloc): Remove.

diff --git a/gcc/doc/interface.texi b/gcc/doc/interface.texi
index b55293d863c51d096c0a91870aac348b885e9471..f6fdc329e1037b60b9f11ef63996c9a5a8307c4f 100644 (file)
--- a/gcc/doc/interface.texi
+++ b/gcc/doc/interface.texi
@@ -69,17 +69,3 @@ values after a @code{longjmp}.  And this is all GCC promises to do,
 because it is very difficult to restore register variables correctly, and
 one of GCC's features is that it can put variables in registers without
 your asking it to.
-
-If you want a variable to be unaltered by @code{longjmp}, and you don't
-want to write @code{volatile} because old C compilers don't accept it,
-just take the address of the variable.  If a variable's address is ever
-taken, even if just to compute it and ignore it, then the variable cannot
-go in a register:
-
-@smallexample
-@{
-  int careful;
-  &careful;
-  @dots{}
-@}
-@end smallexample