Questions about testsuite/document changes.

Steve Kargl sgk@troutmask.apl.washington.edu
Sat Oct 22 03:41:00 GMT 2005


On Fri, Oct 21, 2005 at 05:43:43PM -0700, Uttam Pawar wrote:
> 
> 1) Most of the tests in gfortran.dg have subroutine call "call abort()"
> whenever we want to terminate program after some condition.
> As part of std f95 compliance testing I started compiling and running
> these test with -std=f95 option and I noticed that, all the tests having
> "call abort()" call gave "undefined reference to `abort_'" error. 
> 
> Should we change these or create a new set of these tests (as f95 tests)
> but instead of abort() may be use STOP()?
> Also, these tests (most of them) are still valid for f95.

Unfortunately, a STOP will generate output and I think dejagnu
isn't expecting it.  What we need is an -fintrinsic-allowed=abort
option that specific says that ABORT will be considered to be
an INTRINSIC routine regardless of -std=XXX setting.

It's on my TODO list.

> 2) Should there be an effort to write tests just for the individual
> intrinsic function? Some kind of tests for the intrinsic functions with
> invalid input, expected error/warning output, etc., negative tests?

I think the answer is yes.  We should have test for the intrinsics;
in particularly, corner and special case.  For floating point tests,
we should use relative differences to test for equality, for example,
ABS((TAN(X) - TAN_X_VAl)/ TAN_X_VAL) 

> 3) How does the documentation (user manual) get generated. I know it's
> from corresponding .texi files. But I didn't find the required fortran
> contents available at http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gfortran/
> in any of the .texi files in the mainline cvs tree. 
> I did find all the older g77 intrinsic function documentation in 3.4.1
> release. 
> So, is there plan for creating similar documents for gcc_4.x release?

The documents are created by hand.  Someone sits down and edits
intrinsic.texi.  This is usually a cut/paste/edit exercise.  This
is also a very good way for lurkers to contribute to gfortran. 
You can get a copy of the draft by searching for 007.pdf.

PS:  If you want to contribute, please read the gcc.gnu.org page
about contributing and the need for a copyright assignment.
-- 
Steve



More information about the Fortran mailing list