OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Delete obsolete doc pointed out by Chris Lattner.

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

From-SVN: r84160
This commit is contained in:
James E Wilson 2004-07-06 18:19:16 +00:00 committed by Jim Wilson
parent a064479c83
commit 37bcf311cf
2 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -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.

14
gcc/doc/interface.texi
View File

@ -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