Re: completely static runtime environment



raghavan.viswanathan@xxxxxxxxx wrote:

The compiler books talk of FORTRAN77 compilers using a completely
static environment in which activation records, global variables etc
are all allocated from static memory.

It was common for Fortran 66 compilers to use static data
areas. On machines with a call stack many used the stack for
calling subprograms, such that it wasn't completely static.

OS/360 Fortran compilers used static memory for data,
argument lists, and for storing the return address.

Most DEC Fortran 66 compilers, such as RT-11 and TOPS-10
(I am not sure about the VAX/VMS compilers) used static data
but used the stack for subprogram arguments and return addresses.

I would look at the older Microsoft Fortran compilers,
from the early DOS days.

Otherwise, if you put a SAVE statement in, all local
variables should be static.

-- glen
.



Relevant Pages

  • Re: Is it time to legitimise REAL*8 etc?
    ... Some vendors phased out their F77 compilers over 10 ... No need to support a seperate F77 compiler as, ... experience with F77) that the F95 programming is safer than the F77 ... Authors are not chosing more recent Fortran ...
    (comp.lang.fortran)
  • Re: what is the most suitable Linux platform for Programmers and software developers
    ... C, C++, Perl, Python, Lisp, and a bunch of other languages are supported ... There are FORTRAN compilers, but FORTRAN ... Look at the Linux ...
    (comp.os.linux.misc)
  • Re: Is it time to legitimise REAL*8 etc?
    ... Some vendors phased out their F77 compilers over 10 ... No need to support a seperate F77 compiler as, ... experience with F77) that the F95 programming is safer than the F77 ... COMMONs remain available with any FORTRAN version. ...
    (comp.lang.fortran)
  • Declaration to get 8-bit (or 16-bit) integer?
    ... Supported by all the current compilers that I've tried it on. ... Not likely to become standard in the foreseeable future. ... Syntax standard-conforming, but semantics not guaranteed of course. ... The meaning of the code not obvious to anyone but a Fortran guru. ...
    (comp.lang.fortran)
  • Re: Casting malloc
    ... If he can make a strong case for the diagnostics, ... Uh, again, Fortran is a better tool for some sorts of work. ... familliar what Fortran compilers only in the code they generate; ... Given a variety of hard problems, Fortran consistently came up much faster with default code and no explicit optimizations. ...
    (comp.lang.c)