X-Git-Url: http://git.sourceforge.jp/view?a=blobdiff_plain;f=gcc%2Fdoc%2Finterface.texi;h=f6fdc329e1037b60b9f11ef63996c9a5a8307c4f;hb=2062830ce449c98f1b245e04d4923b6444b35ab3;hp=b55293d863c51d096c0a91870aac348b885e9471;hpb=8a0686b1809b0892bfe9203327d886bbbdd039a7;p=pf3gnuchains%2Fgcc-fork.git

diff --git a/gcc/doc/interface.texi b/gcc/doc/interface.texi
index b55293d863c..f6fdc329e10 100644
--- 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