[RFC] using autogen to audit fortran intrinsics?!

[Bruce Korb]

Hi Daniel,

Attached is my best guess at what you are after.
I didn't do the "run" part, but the "compile" part
should give you an idea about how to approach this.
Attached are:

ftn.def - defines the one intrinsic we are playing with

ftn-test.tpl - produces a long program for testing all
argument variations for each intrinsic.  You might actually
find it easier to manage by producing a separate program
for every invocation of the intrinsic.  Define a "valid
combo" list for the intrinsic and expect a successful
compilation only when the current combination matches
an entry from the "valid combo" list.  This, however, was
what I think you described as what you wanted.

ftn-besj0-comp.ftn - the compile test file for "besj0".

ftn-besj0-run.ftn - the program that should eventually compile & run

ftn-test.sh - a script to compile each of the *.ftn files
and run the ftn-*-run programs

Good luck!

Regards, Bruce

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ftn.def
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20070213/0c75d140/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ftn-test.tpl
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20070213/0c75d140/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ftn-besj0-comp.ftn
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20070213/0c75d140/attachment-0002.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ftn-besj0-run.ftn
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20070213/0c75d140/attachment-0003.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ftn-test.sh
Type: application/x-shellscript
Size: 87 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20070213/0c75d140/attachment.bin>