You are here:   ArielOrtiz.com > Compilers > Project: The Fortran Compiler

Compilers

• News
• Office Hours
• Grades
• Quiz Calendar
• Game Rules
• Online Resources
• Bibliography
• Download Ubuntu
• Syllabus

Project: The Fortran Compiler

Phase	Date	Description	Exemplar	Upload link
1	27-Sep-2013	Lexical analysis.	buttercup-0.1.tgz	SETA
2	14-Oct-2013	Syntactic analysis.	buttercup-0.2.tgz	SETA
3	28-Oct-2013	AST construction.	buttercup-0.3.tgz	SETA
4	14-Nov-2013	Semantic analysis.	buttercup-0.4.tgz	SETA
5	03-Dec-2013	CIL code generation.	buttercup-0.5.tgz	SETA

Notes

• The project must be developed in teams of up to three members.
• Unless stated otherwise, you must only implement those features that are part of the Fortran 77 standard. Do not implement non-standard extensions.

• Features that must not be implemented:

  • Programs with multiple source files (p. 6)
  • Complex numbers and operations (pp. 8, 10).
  • Arrays of more than two dimensions (p. 17).
  • Sequence numbers (columns 73-80, p. 4).
  • Arbitrary index ranges (p. 16).
  • The dimension statement (p. 17).
  • Passing subsections of arrays (p. 21).
  • Passing arrays of different dimensions (pp. 22-23).
  • The block data statement (pp. 26).
  • File I/O (pp. 28-29).
  • Other versions of simple I/O (p. 31).
  • Format statements (pp. 32-33).
  • Numerical software (pp. 35-36).

• Features that are different from what the standard dictates:

  • There is no upper limit on the size of an identifier (names for variables, subroutines, etc.).
  • Blank spaces are significant only as delimiters between identifiers (and reserved words).
  • Statements must start in column 7 but they are not restricted to any upper limit.
  • Any array passed as a parameter to a subprogram must only use an asterisk to indicate that the real array length is unknown be declared using a dummy integer literal to specify its size. In practice, this dummy value will simply be ignored. No other notation should be supported.
  • The continuation character in column 6 can only be + or &.
  • All variables should be explicitly declared. It's an error to use an undeclared variable.
  • Loop variables in do statements must be exclusively of type integer.
  • All instrinsic functions (abs, min, max, sqrt, sin, cos, tan, atan, exp and log) should take real values as parameters and return a real value as its result. No support is needed for double precision values regarding these functions.
  • Subprograms (functions and subroutines) should support recursive calls.
  • Parameters passed to subprograms (functions and subroutines) should use call-by-value evaluation strategy instead of call-by-reference.

Source code examples

Source file	Description	Date added
hello.f	Prints "Hello World!" in the screen.	07-Oct-2013
largest.f	Find the largest of several numbers contained in an array.	07-Oct-2013
fizzbuzz.f	This program prints the numbers from 1 to 100, but for multiples of three it prints "fizz" instead of the number and for the multiples of five it prints "buzz". For numbers which are multiples of both three and five it prints "fizzbuzz".	07-Oct-2013
factorials.f	Computes and prints the factorials of numbers from 0 to 10. Factorials are computed using iterative and recursive functions.	Updated 14-Nov-2013
types.f	Simple examples using all data types and type converversions.	14-Oct-2013
stats.f	Computes the average and standard deviation of 200 numbers.	14-Oct-2013
matrix.f	Simple big matrix manipulation example.	14-Oct-2013
cramer.f	This program uses Cramer's rule to solve a system of 3 linear equations with 3 unknows.	14-Oct-2013
intrinsics.f	Using mathematical intrinsic functions.	4-Nov-2013
pi.f	Computing pi through numerical integration.	4-Nov-2013