Julian Taylor wrote:
> thanks for the explanation.
> Modules are only available with f90 right? f77 files do not have these
> generated interdependencies?
> being able to handle f77 would already be quite good, as it should at
> least cover current scipy.
> One can look at a smarter scheme for f9
On 10.10.2014 21:09, Sturla Molden wrote:
> Julian Taylor wrote:
>
>> There is still one problem in regards to parallelizing fortran 90. The
>> ccompiler.py contains following comment:
>> # build any sources in same order as they were originally specified
>> # especially important for f
Sturla Molden wrote:
> So the Fortran 90 files creates a directed asyclic graph. To compute in
> parallel
Eh, *compile* in parallel.
> Sturla
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-d
Sturla Molden wrote:
> When a Fortran module is compiled, the compiler emits an object file (.o)
> and a module file (.mod). The module file plays the role of a header file
> in C. So when another Fortran file imports the module with a use statement,
> the compiler looks for the module file. Beca
Julian Taylor wrote:
> There is still one problem in regards to parallelizing fortran 90. The
> ccompiler.py contains following comment:
> # build any sources in same order as they were originally specified
> # especially important for fortran .f90 files using modules
>
> This indicate
hi,
To speed up compilation of extensions I have made a PR to compile
extension files in parallel:
https://github.com/numpy/numpy/pull/5161
It adds the --jobs/-j flags to the build command of setup.py which
defines the number of parallel compile processes.
E.g.
python setup.py build --jobs 4 insta
