PR30372
Steve Kargl
sgk@troutmask.apl.washington.edu
Mon Feb 12 03:14:00 GMT 2007
On Mon, Feb 12, 2007 at 03:36:46AM +0100, Daniel Franke wrote:
>
> In PR30372, Steve Kargl wrote:
> > So, I think we need to audit the intrinsics to see were we need to
> > fix up the inconsistencies and documentation.
>
> I started to draft a skript to create testcases that deterministically test
> anything with everything.
Does it test for real(10) and/or real(16)?
> Now I'd like to know how to proceed with found inconsistencies: a PR
> for every intrisic affected (details as usual) and a meta-bug to track
> them?
This is probably the best way to keep track of things. If we had
a single PR, it could get bogged down by a single intrinsic procedure
that is difficult to fix.
> It is to assume that, eventually, there will be loads of (mostly generated)
> test files. Shall we consider to add them to the fortran test harness?
This touchs on an observation of Brooks' that the tests in the
testsuite (which test intrinsics), typically only test the
constant folding in the frontend. We should devise tests for
both constant folding and the library routines. I think the
test can go into gfortran.dg for now. At some point, we may
move things into libgfortran.dg.
--
Steve
More information about the Fortran
mailing list