Library testsuite

[Tobias Schlüter]

FX Coudert wrote:
> I'll just ask a silly question:
> 
>> I divided the libgfortran testsuite into two subdirectories [...] the 
>> tests in intrinsics cycle through the usual set of options.
> 
> If the tests in intrinsics are supposed to cover intrinsics for which 
> code is emitted directly by the front-end, why are we having them in the 
> library testsuite rather than the front-end testsuite?

Just a matter of organizing our testcases, we have lots of them and 
they're in no way organized.  I don't know if that buys us anything.

> Here's what I was thinking of:
>   1. put all I/O tests in an I/O directory in the libgfortran testsuite
>   2. create also a intrinsics directory, which is run with only one 
> optimization level, and
>   3. we clearly document the difference, and start moving stuff from 
> gfortran.dg to the libgfortran testsuite slowly, by taking care of 
> whether the test is actually testing front-end emitted code or rather 
> library calls
>   4. exercise same care when deciding where a new test will end up
> 
> Phase 3 can take some time, but it's OK because it will only take a 
> little more time than ideal, but we won't be laking testsuite coverage.

All of this sounds good, but I'm worried that we will have testcases 
dangling around in the wrong places when our implementations change 
from, say, calling a library function to inline code.

- Tobi