Differences between revisions 452 and 453
Revision 452 as of 2016-09-22 08:06:38
Size: 22798
Editor: PaulThomas
Comment:
Revision 453 as of 2016-09-22 08:29:40
Size: 22800
Editor: PaulThomas
Comment:
Deletions are marked like this. Additions are marked like this.
Line 49: Line 49:
 * Bug Bashing (status 7th October 2015; incl. some double counting)
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=regress&component=fortran&component=libfortran&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|Regressions]] 47 bugs 10 assigned
 * Bug Bashing (status 22nd September 2016; incl. some double counting)
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?short_desc_type=allwordssubstr&short_desc=regress&component=fortran&component=libfortran&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|Regressions]] 56 bugs 10 assigned
Line 53: Line 53:
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=wrong-code&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where wrong code is produced]] 97 bugs 13 assigned [often triggered for special cases only]
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=ice-on-valid-code,rejects-valid,wrong-code,compile-time-hog,memory-hog,link-failure&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where a valid Fortran program is not accepted (internal compiler error, wrongly rejected), wrong code is produced or where the compile time or memory is excessively high]] 208 24 assigned bugs
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=accepts-invalid,ice-on-invalid-code&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where invalid code is accepted or gives an internal compiler error]] 103 bugs 5 assigned
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=diagnostic&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs which show where the diagnostics can be improved]] 147 bugs 5 assigned
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|All reports (bug reports, feature requests etc.)]]: 766 reports
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=wrong-code&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where wrong code is produced]] 93 bugs 8 assigned [often triggered for special cases only]
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=ice-on-valid-code,rejects-valid,wrong-code,compile-time-hog,memory-hog,link-failure&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where a valid Fortran program is not accepted (internal compiler error, wrongly rejected), wrong code is produced or where the compile time or memory is excessively high]] 202 21 assigned bugs
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=accepts-invalid,ice-on-invalid-code&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs where invalid code is accepted or gives an internal compiler error]] 115 bugs 6 assigned
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&keywords_type=anywords&keywords=diagnostic&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|PRs which show where the diagnostics can be improved]] 127 bugs 5 assigned
  * [[https://gcc.gnu.org/bugzilla/buglist.cgi?component=fortran&component=libfortran&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED|All reports (bug reports, feature requests etc.)]]: 853 reports

gfortran — the GNU Fortran compiler, part of GCC

Gfortran is the name of the GNU Fortran project, developing a free Fortran 95/2003/2008 compiler for GCC, the GNU Compiler Collection. The gfortran development effort uses an open development environment in order to attract a larger team of developers and to ensure that gfortran can work on multiple architectures and diverse environments.

This wiki contains links to binary packages for gfortran, up-to-date status of the compiler, recently fixed bugs, etc. You can find here our "getting started" web page for new users of gfortran.

The official homepage for gfortran also contains a limited amount of general information about the project, its goals and the ways you can contribute.

Using gfortran

For gfortran developers



Manuals and other documentation

GFortran documentation is included with the GCC documentation, which is available from the GCC website. There is documentation for released compilers, and also documentation for the latest snapshot from the development tree. The manuals are re-generated nightly.


Reporting bugs

You can report bugs in GCC bugzilla. You can look for existing bugs, track bug fixing progress, and report new bugs there. The list of all open gfortran bugs (including enhancement requests and low-priority bugs) can be found here. Before submitting a bug report, please update your version of gfortran to the latest available release of GCC. For example, if you find a bug with gfortran 4.0.2, then upgrade to at least GCC 4.1.0 and see if the bug is still present.

There is a separate page for the most wanted gfortran bugs, which contains a list of bugs that block gfortran from building major packages. Some ideas for enhancing gfortran can also be of interest...

Use the gfortran mailing list, fortran@gcc.gnu.org , to ask the gfortran community your questions, and report bugs if you are uncertain on how to handle bugzilla. We'll be glad to help!


gfortran compliance test coverage matrix (initial version)


CategoryCategory

None: GFortran (last edited 2016-09-22 08:29:40 by PaulThomas)