+++ /dev/null
-Contributors to G95
-
-If we have left anyone out, please let us know:
-<gcc-g95-devel@lists.sourceforge.net>
-
-
-Major code contributors
-----------------------------------
-Andy Vaught
-Katherine Holcomb
-Steven Bosscher
-Paul Brook
-Arnaud Desitter
-Canqun Yang
-Xiaoqiang Zhang
-
-
-Small patches (no copyright assignment)
-----------------------------------
-Niels Kristian Bech Jensen
-Steven G. Johnson
-Tobias Schlüter
-
-
-Helpful comments
-----------------------------------
-Erik Schnetter
-Steven G. Kargl
-W. Clodius
-Claus Fischer
-Toon Moene
-Richard T. Henderson
-
+2004-08-31 Tobias Schlueter <tobias.schlueter@physik.uni-muenchen.de>
+
+ * CONTRIB, NEWS, README, TODO: Remove obsolete files.
+
2004-08-31 Tobias Schlueter <tobias.schlueter@physik.uni-muenchen.de>
PR fortran/17244
+++ /dev/null
-2003-01-06
-This project is a fork of the original G95 project. The fork has the
-support of the GCC community. We still persue mostly the same goals
-as the original project, but we hope we can attrack more developers
-through better cooperation and communication, and we target quicker
-inclusion in GCC.
-
+++ /dev/null
-The goal of the gcc-g95 project is to create a Free (as
-in speech) Fortran 95 compiler. The code has been donated
-to the Free Software Foundation for inclusion in GCC, thE
-GNU Compiler Collection.
-
-WARNING:
-
-G95 is still under development. Perusing the g77 source, we estimate
-that about 200,000 lines of code will be necessary to fully implement
-g95. Currently, G95 is about 70,000 lines long, making it about
-version 0.3.
-
-The current g95 can generate code for most legal Fortran 77 programs,
-and we're getting close to being able to compile most Fortran 95
-programs as well. The generated code may still be quite poor, however.
-Part of this is a back-end issue, since we're using the Work-In-Progress
-tree-ssa infrastructure.
-
+++ /dev/null
-TODO
-
-Parser fixes:
-------------
-
-In a constant format string given to a data transfer statement, the
-locus of any problems in the string isn't guaranteed to come out
-right, because there is not a 1:1 correspondence between source
-characters and characters in the string. This scheme totally doesn't
-work for format strings that are longer than a physical line.
-
-Fix IMPLICIT to allow forward references of derived types.
-
-Array issues in expressions and intrinsics.
-
-Resolve scoping issues. Create symbols in correct namespaces.
-
-Finish resolution phase.
-
-Finish compiler side of intrinsic functions.
-
-Allow init exprs to be numbers raised to integer powers (negative too).
-
-See about making emacs-parsable error messages.
-
-
-Biggies:
---------
-
-Interface to code generator.
-
-Complete runtime library.
-
-
-Known bugs:
------------
-
-Failure to set the expr_locus field in g95_expr structures.
-
-
-And for the really pedantic
----------------------------
-
-Fix INCLUDE such that it only appears on a single line. The current
-code allows things like:
-
- 0I
- 1NCLUDE "filename"
-
-or its free form equivalent:
-
-I&
-NCLUDE "filename"
-
-This is explicitly forbidden by the F95 standard (ref. section 3.4).
-