gfortran testing

Steve Kargl sgk@troutmask.apl.washington.edu
Tue Oct 25 18:16:00 GMT 2005


On Tue, Oct 18, 2005 at 03:18:49PM -0700, Uttam Pawar wrote:
> 
> I'm thinking of bulking up the fortran testsuite w.r.t. fortran
> 95 standard. I got the copy of INCITS+ISO+IEC+1539-1-1997+(R2003).pdf
> today.

Good.  This is, IMHO, sorely needed.

> Does the maintainer of gfortran or any one else has any ideas about
> the missing tests for particular or any part of fortran standard?

Many of the tests in the testsuite are from bug reports.  These
do not necessarily apply to any specific constraint in the standard.
We could use better coverage in the testsuite.,

> Where and how should I start?

Good question.  I would start with language features that I know.
Check that gfortran correctly handles constraints and see what 
happens with restrictions.  For example, I don't use namelist,
so I could not write concise test cases; OTOH, I do use modules
so I would investigate gfortran's module capabilities.

> Or, there is no other way but to go through the whole document
> and gfortran test suite and start figuring it out?

I would not worry about duplicate tests at this point in time.
If people find "gmake check-gfortran" takes too long with 
the additional conformance testing, we can add a "gmake
check-gfortran-standard" target and testsuite/gfortran.standard.
Note, this can get quite tricky.  For the one line program "END",
there are numerous things to check because of free and fixed 
form input.  All of the following are 1 liners (ignoring comments).

C FIXED OR FREE
      END

C FIXED BUT NOT FREE
      E    N    D

END  ! Free form but not fixed

-- 
Steve



More information about the Fortran mailing list