verifying argument counts and types
in [Fortran]
|
Prev: managing identities
Next: Call Tree Generator
From: e p chandler on 2 Feb 2010 19:40 "Lynn McGuire" <lmc(a)winsim.com> wrote in message news:mvKdnYNrbtDuO_XWnZ2dnUVZ_tWdnZ2d(a)supernews.com... >> Is it possible that what you think are zero-initialization problems >> are really symptoms of some other kind of bug? Your project is already > > Nope. We dont have the runtime problems unless I turn off > the zero-init and universal save options. > >> old, and it won't be finished any time soon. Perhsps it would be worth >> the effort to re-engineer it with a F95+ compiler that offers better >> diagnostics and interface checking. I'm sure that Richard would say >> that it's far cheaper in the long run to do it right the first time. > > The first time this software was released was in 1969 > on the old UCC system (Univac 1108) ... Yeow. I worked on one of these systems in the early 80s. > This is released commercial software in use by 1000s of > customers. OK. [I was going to say something about the Comet flying really well ... for a while.] --- e > Lynn
From: analyst41 on 2 Feb 2010 21:29 On Feb 2, 1:10 pm, Lynn McGuire <l...(a)winsim.com> wrote: > Is there some way that I can verify our argument call > counts and argument types ? We are locked into a F77 > compiler because of some zero initialization problems > that we have not been able to find. We have 650,000 > lines of f77 code in about 5,000 files with probably > 6,000 subroutines and functions. > > Thanks, > Lynn Would be possible to write a fortran program to check argument lists? I have, in the past, written customizable diff routines in Fortran to run against Fortran programs (for example you can reinitialize the diff count to zero for each new subprogram).
From: robin on 3 Feb 2010 18:09 <analyst41(a)hotmail.com> wrote in message news:a0e21ced-4b0c-4e7b-9b6f-f2fd5459ff69(a)o16g2000vbf.googlegroups.com... On Feb 2, 1:10 pm, Lynn McGuire <l...(a)winsim.com> wrote: >> Is there some way that I can verify our argument call >> counts and argument types ? We are locked into a F77 >> compiler because of some zero initialization problems >> that we have not been able to find. We have 650,000 >> lines of f77 code in about 5,000 files with probably >> 6,000 subroutines and functions. > >> Thanks, >> Lynn >Would be possible to write a fortran program to check argument lists? That wouldn't do what Lynn wanted, which was to check argument types as well as numbers of arguments. In any case, apparently, that can be done with an F95 compiler. >I have, in the past, written customizable diff routines in Fortran to >run against Fortran programs (for example you can reinitialize the >diff count to zero for each new subprogram).
From: Lynn McGuire on 3 Feb 2010 18:38 > Intel Fortran has a "generated interface checking" option. You compile > your sources with -warn interface (/warn:interface on Windows) and it > automatically generates interface blocks and modules for subroutines and > functions and checks calls against them, warning you of mismatches. For > best success, I suggest two builds, leaving the generated .mod files in > place after the first build, because a call to a routine that has not > yet been compiled can't be checked. Does IVF create a .MOD file for each .F file ? Do the ..MOD file(s) have to put into a certain area for the .F files to look them (my .F files are scattered over about 100 directories) ? Thanks, Lynn
From: glen herrmannsfeldt on 4 Feb 2010 01:14
robin <robin_v(a)bigpond.com> wrote: (snip, someone wrote) >> Would be possible to write a fortran program to check >> argument lists? > That wouldn't do what Lynn wanted, which was to check > argument types as well as numbers of arguments. It would be possible, but not easy. It takes much of the front end of a Fortran compiler to do it. Fortran compilers lately are rarely written in Fortran. -- glen |