gfortran: Open Projects

This list is probably not complete, but it seems long enough already. Some of the items are also filed as a bug reports in our bugzilla problem report database as indicated below.

Parser

• Give NULL() pointer correct attributes.
• Fix array constructor handling in expressions and intrinsics.
• Complete implementation of section 14.1.2: Procedure type resolution rules.
• Implement resolution of COMMON blocks and EQUIVALENCE associations.
• Fix other issues in the type/name resolution phase.
• Improve diagnostics, some of them are cryptic or point to the wrong place.
• Improve error printing for diagnostics within simplification functions.
• See about making Emacs-parsable error messages.
• Do not bother storing non-parameter variable initializers in modules.
• Check for improper (full section) use of assumed size arrays.
• Do something about the expr->symbol vs expr->value.function.esym mess.

Middle-end Interface

• Implement functions returning derived types.
• Support alternate ENTRY points (PR13082).
• Correctly initialize POINTER variables.
• Handle constant initializers for derived types.
• Handle character string parameters.
• Implement DATA.
• Implement character variables in COMMON and EQUIVALENCE blocks.
• Finish compiler side of intrinsic functions.
• Produce debugging information.
• Improve generated code (lots of room for that).
• Do not create array descriptors where we do not need them (temporary arrays).
• Support large (unexpanded) array constructors as variable initializers.
• Use of array parameters in array declarations.
• Teach the scalarizer bounds calculation code about functions.

Run time library

• Complete the implementation of derived type I/O (PR13278 and PR13280).

g77 compatibility

• Implement Hollerith data (PR16531).
• Implement the -fugly- family of compiler options.
• Fix g77/f2c compatibility for returning complex numbers, and other wierdness.

Testsuite

• Figure out what causes the remaining testsuite parse failures.
• Add more testcases to the execution test suite.
• Add negative tests (i.e. check invalid code is rejected).

Documentation

• Finish (start?) infopages and other documentation.
• Split out an "invoke.texi" so that a man page can be generated automatically.
• Maintain web page.

Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.

These pages are maintained by the GCC team.

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help.
Please send comments on these web pages and the development of GCC to our developer mailing list at gcc@gnu.org or gcc@gcc.gnu.org. All of our lists have public archives.

Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110, USA.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

Last modified 2006-06-21