Commit 8182dc46 by Craig Burley Committed by Craig Burley

Add AUTOMATIC to list of unsupported extensions

From-SVN: r25706
parent 827e80cc
Thu Mar 11 17:32:55 1999 Craig Burley <craig@jcb-sc.com>
* g77.texi: Add AUTOMATIC to list of unsupported extensions.
Sat Mar 6 02:28:35 1999 Craig Burley <craig@jcb-sc.com> Sat Mar 6 02:28:35 1999 Craig Burley <craig@jcb-sc.com>
Warn about non-Y2K-compliant intrinsics: Warn about non-Y2K-compliant intrinsics:
......
...@@ -14,7 +14,7 @@ ...@@ -14,7 +14,7 @@
@c %**start of header @c %**start of header
@setfilename g77.info @setfilename g77.info
@set last-up-date 1999-03-06 @set last-up-date 1999-03-11
@set version-g77 0.5.24 @set version-g77 0.5.24
@set email-general egcs@@egcs.cygnus.com @set email-general egcs@@egcs.cygnus.com
@set email-bugs egcs-bugs@@egcs.cygnus.com @set email-bugs egcs-bugs@@egcs.cygnus.com
...@@ -11999,6 +11999,7 @@ GNU Fortran language: ...@@ -11999,6 +11999,7 @@ GNU Fortran language:
* Intrinsics in PARAMETER Statements:: * Intrinsics in PARAMETER Statements::
* SELECT CASE on CHARACTER Type:: * SELECT CASE on CHARACTER Type::
* RECURSIVE Keyword:: * RECURSIVE Keyword::
* AUTOMATIC Statement::
* Popular Non-standard Types:: * Popular Non-standard Types::
* Full Support for Compiler Types:: * Full Support for Compiler Types::
* Array Bounds Expressions:: * Array Bounds Expressions::
...@@ -12157,6 +12158,30 @@ designed to do recursion. ...@@ -12157,6 +12158,30 @@ designed to do recursion.
All recursive code can be rewritten to not use recursion, All recursive code can be rewritten to not use recursion,
but the result is not pretty. but the result is not pretty.
@node AUTOMATIC Statement
@subsection @code{AUTOMATIC} Statement
@cindex @code{AUTOMATIC} statement
@cindex statements, @code{AUTOMATIC}
@cindex automatic variables
@cindex variables, automatic
@code{g77} doesn't support the @code{AUTOMATIC} keyword that
@code{f2c} does.
It is not yet clear exactly what this statement would achieve.
The semantic equivalent would be provided by @code{RECURSIVE}
combined with lack of @code{SAVE}.
In that sense, perhaps all it would provide is an
overriding of an unadorned (blanket) @code{SAVE} statement
for specific variables.
It might also serve as a hint to the compiler that placing
even a very large array on the stack is acceptable.
Perhaps it should disallow @code{DATA}
or other specification of any initial values
for affected variables as well.
@node Increasing Precision/Range @node Increasing Precision/Range
@subsection Increasing Precision/Range @subsection Increasing Precision/Range
@cindex -r8 @cindex -r8
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment