[petsc-dev] Case TS005062693 - XLF: ICE in xlfentry compiling a module with 358 subroutines
Satish Balay
balay at mcs.anl.gov
Wed Mar 17 09:44:38 CDT 2021
On Wed, 17 Mar 2021, Blaise A Bourdin wrote:
>
>
> On Mar 16, 2021, at 11:17 PM, Barry Smith <bsmith at petsc.dev<mailto:bsmith at petsc.dev>> wrote:
>
>
> So it actually does not load everything at the call to use but waits until the subroutine definitions and then only loads what you ask to import?
>
> Sorry, this is odd, with C include or python import it immediately loads up everything as soon as it sees the include or import, there is no way later to say "wo hoarsy I didn't really mean you should get everything I asked, for please only load up a subset".
>
>
> But then Fortran was always weird, when I saw presentations of the Fortran standards committee members I always felt like they read every third page of some computer science book but never realized they missed many of the pages.
>
> Which proves that they know their target audience ;)
>
> >From the standpoint of somebody who also read every third page of a computer science book, fortran modules sounded like a good idea on the paper (I basically think of them as auto-generated header files), but they are miserable in practice, and in particular a major block to cross compiler compatibility since the format of .mod file was left to the discretion of the compiler writers.
>
Not just (a)cross compiler - different versions of gfortran are incompatible with each other's .mod format..
Satish
> Blaise
>
> --
> A.K. & Shirley Barton Professor of Mathematics
> Adjunct Professor of Mechanical Engineering
> Adjunct of the Center for Computation & Technology
> Louisiana State University, Lockett Hall Room 344, Baton Rouge, LA 70803, USA
> Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 Web http://www.math.lsu.edu/~bourdin
>
>
More information about the petsc-dev
mailing list