To all!
Thanks to everyone that has participated in this thread so far. Several
participants has reported similar experiences. To me this is an indication
that the problem deserves more attention and hopefully one of the vendors is
willing to explain to us all the intricacies associated with USE and module
files. I have always had the feeling that the module files contains the
procedure interfaces. When we USE the interfaces a read from the module file
and the compiler does a consistency check automatically. If this was the
case I can't understand the time nor the memory consumption of the compiler.
Obviously a lot more must be going on and I would be greatful if one of the
vendors would be kind enough to enlighten us. It would be great to hear if
something can be done about it.
To Alvaro!
I use PRIVATE as the default for all my modules and I also use ONLY clauses
with my USE statements. The use of ONLY clauses I know for a fact helps. In
one example I saw that the memory use during compilation nearly halved.
Therefore I use ONLY clauses as standard everywhere.
Magne Rudshaug
----- Original Message -----
From: "Alvaro Fernandez" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, November 13, 2002 3:32 PM
Subject: Re: More on slow compilation!
> I only got heavily into programming with Fortran 90 - my previous codes
> using Fortran 77 were basically exercises, so I never experienced the
> slowdown I've heard people refer to. (It doesn't surprise me, though.)
>
> M. Rudshaug, the originator of the thread, says that the code is
> logically organized (I was the one who brought it up. Sorry... :-)).
> However, I would still be curious to find out whether ONLY is being used
> to control access in lieu of PRIVATE in the code. Is it?
>
> Alvaro Fernandez
>
>
>
>
> -----Original Message-----
> From: Fortran 90 List [mailto:[log in to unmask]] On Behalf
> Of Keith Lindsay
> Sent: Wednesday, November 13, 2002 8:05 AM
> To: [log in to unmask]
> Subject: Re: More on slow compilation!
>
> Hello,
>
> Your description of module usage forcing the compiler to use an
> apparently excessive amount of memory is very similar to a problem I had
> some time ago with a Compaq compiler (over a year ago). In my situation,
> I could not actually compile the full code because the system ran out of
> memory. The OS refused to give the compiler the > 2Gb it requested.
> The file it was compiling at the time malloc's failed was a pretty
> simple one that happened to use many modules. This problem was reported
> to the vendor and they were able to generate a patch that solved it. I
> suggest contacting your vendor.
>
> Hope this helps, Keith
>
> ******************************************************************
> Keith Lindsay http://www.cgd.ucar.edu/oce/klindsay/
> email: [log in to unmask] phone: 303-497-1722 fax: 303-497-1700
>
|