On Nov 14, 2016, at 12:19 PM, Mahmood Naderan wrote:
>
> The output is not meaningful for me.
> If I add --showme option, the output is http://pastebin.com/FX1ks8iW
--showme does not compile anything. It just shows you what underlying command
line *would* be invoked (if you dropped the --showm
The output is not meaningful for me.
If I add --showme option, the output is http://pastebin.com/FX1ks8iW
and if I drop --showme, the output is http://pastebin.com/R1QFYVBe
Please search for xml.F. Do you have any idea?
Regards,
Mahmood
___
users mail
Remember that mpifort is just a wrapper over your underlying fortran compiler.
If your fortran compiler can't compile your Fortran code, then neither can
mpifort.
You can use the "--showme" option to mpifort to show you the command line that
it is invoking under the coverts. E.g.:
mpifor
Hi,
The following mpifort command fails with a syntax error. It seems that the
code is compatible with old gfortran, but I am not aware of that. Any idea
about that?
mpifort -ffree-form -ffree-line-length-0 -ff2c -fno-second-underscore
-I/opt/fftw-3.3.5/include -O3 -c xml.f90
xml.F:641.46:
Hi Joesph,
I don’t have a solution to your issue, but I’ve found that the valgrind mpi
wrapper is necessary to eliminate many of the false positives that the
suppressions file can’t.
http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mpiwrap.gettingstarted
You should LD_PRELOAD the libmp
All,
I am investigating an MPI application using Valgrind and see a load of
memory leaks reported in MPI-related code. Please find the full log
attached. Some observations/questions:
1) According to the information available at
https://www.open-mpi.org/faq/?category=debugging#valgrind_clean
Dear developers,
also the following issue is defintely raised by a misconfiguration of Open MPI,
SIGSEGV's in 'ompi_info' isn'n a good thing, thus this one mail.
Just call:
$ export OMPI_MCA_mtl="^tcp,^ib"
$ ompi_info --param all all --level 9
... and take a look at the below core dump of 'ompi
