Re: gfortran, g95, and dual-core

Tim Prince wrote:
> For example,(with f77 code) if the makefile
runs fsplit on a single source file, causes each subroutine to be
rebuilt separately, then combines individual objects into a single large
object, make doesn't automatically see the possibility of building the
individual objects in parallel.

Many people use nested makefiles. That is, running make from
inside the makefile. It would seem that if you ran fsplit,
then ran make on the resulting files it should be able to build
in parallel.

I wonder, though, if compilers are using so much memory as to
start swapping it wouldn't help much to run them in parallel.

-- glen

.

Relevant Pages

  • Re: gfortran, g95, and dual-core
    ... > For example,(with f77 code) if the makefile ... then combines individual objects into a single large ... The fsplit example is not representative of my habits, which are to keep all routines in separate files and put everything but the main into static link libraries. ...
    (comp.lang.fortran)
  • Re: gfortran, g95, and dual-core
    ... > For example,(with f77 code) if the makefile ... then combines individual objects into a single large ... utilities with more difference from recognized standards. ...
    (comp.lang.fortran)
  • Re: gfortran, g95, and dual-core
    ... For example,if the makefile ... then combines individual objects into a single large ... interested in the 2 level relocatable object build. ... Compiler vendors don't advocate 2 level relocatable object builds. ...
    (comp.lang.fortran)
  • Re: gfortran, g95, and dual-core
    ... Tim Prince wrote: ... For example,(with f77 code) if the makefile ... then combines individual objects into a single large ...
    (comp.lang.fortran)