[patch] Re: GFortran testsuite problems with "dg-do compile"

[Tobias Burnus]

Hi,

Brooks Moses wrote:
> Elsewhere in the testsuite, I see that we have one "dg-do assemble"
> and one "dg-do link", which I presume will generate the object code
> and link it, respectively, yes?
Yes, see: http://gcc.gnu.org/wiki/HowToPrepareATestcase

Valid actions for dg-do

* preprocess - only run the preprocessor on the file.
* compile - compile the file and emit the assembly code.
* assemble - compile the file and assemble the assembly code, producing
an object binary.
* link - compile, assemble and link the testcase, producing an executable.
* run - compile, assemble and link the testcase, and run the generated
executable. The executable must then return with exit code 0 for the
test to be successful.

I think, gfortran can live with "compile" and "run" only:
- Valid program - not only compile, assemble or link them, but also run them
- Invalid programs - they cannot be assembled or linked as the compiler
complains already

The others (assemble, link) are more interesting for the middle end, I
would think.

We currently have:

link:  char_result_11.f90
assemble: same_name_1.f90

I converted the first one to a "run" and the second one to a "link" to
increase testing.
Ok for the trunk?

Tobias


2006-12-19  Tobias Burnus  <burnus@net-b.de>

    * gfortran.dg/char_result_11.f90: Use 'dg-do "run"' instead of "link".
    * gfortran.dg/same_name_1.f90: Use 'dg-do "link"' instead of "assemble".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testsuite.diff
Type: text/x-patch
Size: 1687 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20061219/7273cb10/attachment.bin>