mpichbot
commented
8 years ago Originally by michael on 2009-07-13 16:29:22 -0500
This message has 0 attachment(s)
Closed mpichbot closed 8 years ago
mpichbot
commented
8 years ago Originally by michael on 2009-07-13 16:29:22 -0500
This message has 0 attachment(s)
mpichbot
commented
8 years ago Originally by chan on 2009-07-13 16:57:56 -0500
I recall there were some bugfixes related the mpi wrappers back then in 1.0.6. Could you try the latest mpich2, 1.1, and let me know if the problem persists ? Or if you have a simple f90 code that you can send me to demonstrate the problem.
A.Chan
mpichbot
commented
8 years ago Originally by michael on 2009-07-13 17:44:50 -0500
On Mon, 2009-07-13 at 21:57 +0000, mpich2 wrote:
> -----------------------------------------------------+----------------------
> Reporter: michael <michael.bane@manchester.ac.uk> | Owner:
> Type: bug | Status: new
> Priority: major | Milestone:
> Component: mpich2 | Resolution:
> Keywords: |
> -----------------------------------------------------+----------------------
>
>
> Comment (by chan):
>
> I recall there were some bugfixes related the mpi wrappers back then in
> 1.0.6.
> Could you try the latest mpich2, 1.1, and let me know if the problem
> persists ?
> Or if you have a simple f90 code that you can send me to demonstrate the
> problem.
>
> A.Chan
>
see below and attachments
mike@130-88-154-30:~/MKB/Fortran/MPI> rm Unknown.*
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*;mpif90 pi3f90.f90 && mpirun
-l -n 2 ./a.out
ls: cannot access Un*: No such file or directory
0: pi is approximately: 3.1415926535897229 Error is:
0.0000000000000702 wall clock time= 12.116secs on 2PEs
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*
ls: cannot access Un*: No such file or directory
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*;mpif90 -mpe=mpilog
pi3f90.f90 && mpirun -l -n 2 ./a.out
ls: cannot access Un*: No such file or directory
0: pi is approximately: 3.1415926535897229 Error is:
0.0000000000000702 wall clock time= 14.922secs on 2PEs
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*
ls: cannot access Un*: No such file or directory
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*;mpif77 --freeform -ff90
-mpe=mpilog pi3f90.f90 && mpirun -l -n 2 ./a.out
ls: cannot access Un*: No such file or directory
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-
linux/bin/ld:pi3f90.f90: file format not recognized; treating as linker script
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-
linux/bin/ld:pi3f90.f90:1: syntax error
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*;mpif77 --freeform -ff90
-mpe=mpilog pi3f90.f && mpirun -l -n 2 ./a.out
ls: cannot access Un*: No such file or directory
f771: error: unrecognized option `-ffreeform'
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*;mpif77 --free-form -ff90
-mpe=mpilog pi3f90.f && mpirun -l -n 2 ./a.out
ls: cannot access Un*: No such file or directory
0: pi is approximately: 3.1415926535897229 Error is:
0.0000000000000702 wall clock time= 27.075secs on 2PEs
0: Writing logfile....
0: Enabling the Default clock synchronization...
0: Finished writing logfile Unknown.clog2.
mike@130-88-154-30:~/MKB/Fortran/MPI> ls Un*
Unknown.clog2
Originally by michael on 2009-07-13 17:44:50 -0500
Attachment added: pi3f90.f (2.0 KiB)
Added by email2trac
mpichbot
commented
8 years ago Originally by michael on 2009-07-13 17:44:50 -0500
Attachment added: pi3f90.f90 (2.0 KiB)
Added by email2trac
mpichbot
commented
8 years ago Originally by chan on 2009-07-14 00:26:11 -0500
Can you send us the output of "mpich2version" ?
BTW, I just tried a similar pi3f90.f90 with mpif90 (compiled with gfortran) -mpe=mpilog, everything works.
mpichbot
commented
8 years ago Originally by michael bane on 2009-07-14 02:43:34 -0500
On 14 Jul 2009, at 06:26, mpich2 wrote:
> -----------------------------------------------------
> +----------------------
> Reporter: michael <michael.bane@manchester.ac.uk> | Owner:
> chan
> Type: bug | Status:
> new
> Priority: major | Milestone:
> Component: mpich2 | Resolution:
> Keywords: |
> -----------------------------------------------------
> +----------------------
>
> Changes (by chan):
>
> * owner: => chan
>
> Comment:
>
> Can you send us the output of "mpich2version" ?
mike@130-88-154-30:~> mpich2version
MPICH2 Version: 1.0.6
MPICH2 Release date: Unknown, built on Tue Sep 25 19:40:55 BST 2007
MPICH2 Device: ch3:sock
MPICH2 configure: -prefix=/software/64/mpich2-1.0.6
MPICH2 CC: gcc -O2
MPICH2 CXX: c++ -O2
MPICH2 F77: g77 -O2
MPICH2 F90: ifort -O2
MPICH2 Patch level: none
>
> BTW, I just tried a similar pi3f90.f90 with mpif90 (compiled with
> gfortran) -mpe=mpilog, everything works.
>
> --
> Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/721#comment:4
> >
Originally by Anthony Chan on 2009-07-14 02:56:18 -0500
----- "mpich2" <mpich2-maint@mcs.anl.gov> wrote:
> > Can you send us the output of "mpich2version" ?
>
> mike@130-88-154-30:~> mpich2version
> MPICH2 Version: 1.0.6
> MPICH2 Release date: Unknown, built on Tue Sep 25 19:40:55 BST
> 2007
> MPICH2 Device: ch3:sock
> MPICH2 configure: -prefix=/software/64/mpich2-1.0.6
> MPICH2 CC: gcc -O2
> MPICH2 CXX: c++ -O2
> MPICH2 F77: g77 -O2
> MPICH2 F90: ifort -O2
> MPICH2 Patch level: none
Can you use a later version of mpich2 like 1.0.8p1 or preferably
1.1 ? Since you have intel fortran compiler, you could set
F77=ifort and F90=ifort as part of configure command.
A.ChanOriginally by michael bane on 2009-07-14 03:17:02 -0500
On 14 Jul 2009, at 08:56, mpich2 wrote:
> -----------------------------------------------------
> +----------------------
> Reporter: michael <michael.bane@manchester.ac.uk> | Owner:
> chan
> Type: bug | Status:
> new
> Priority: major | Milestone:
> Component: mpich2 | Resolution:
> Keywords: |
> -----------------------------------------------------
> +----------------------
>
>
> Comment (by Anthony Chan):
>
> {{{
>
>
> ----- "mpich2" <mpich2-maint@mcs.anl.gov> wrote:
>
>
>>> Can you send us the output of "mpich2version" ?
>>
>> mike@130-88-154-30:~> mpich2version
>> MPICH2 Version: 1.0.6
>> MPICH2 Release date: Unknown, built on Tue Sep 25 19:40:55 BST
>> 2007
>> MPICH2 Device: ch3:sock
>> MPICH2 configure: -prefix=/software/64/mpich2-1.0.6
>> MPICH2 CC: gcc -O2
>> MPICH2 CXX: c++ -O2
>> MPICH2 F77: g77 -O2
>> MPICH2 F90: ifort -O2
>> MPICH2 Patch level: none
>
> Can you use a later version of mpich2 like 1.0.8p1 or preferably
> 1.1 ? Since you have intel fortran compiler, you could set
> F77=ifort and F90=ifort as part of configure command.
Anthony, I'll have to speak to the sys admin about that.... I was
hoping there's a way to persuade mpif90 cmd to get correct libs etc?
ta, MichaelOriginally by chan on 2009-07-24 00:24:51 -0500
resolving this for now until we hear more from the user.
mpichbot
commented
8 years ago Originally by michael.bane@manchester.ac.uk on 2009-07-24 03:58:53 -0500
was there no way to just use the flags to over-ride and use correct
lib/lib paths?
ta, M
On 24 Jul 2009, at 06:24, mpich2 wrote:
> #721: mpich2, gfortran, F90 files and MPE
> -----------------------------------------------------
> +----------------------
> Reporter: michael <michael.bane@…> | Owner:
> chan
> Type: bug | Status:
> closed
> Priority: major | Milestone:
> Component: mpich2 |
> Resolution: worksforme
> Keywords: |
> -----------------------------------------------------
> +----------------------
> Changes (by chan):
>
> * status: new => closed
> * resolution: => worksforme
>
>
> Old description:
>
>> {{{
>>
>> I'm wishing to use -mpe=mpilog for F90 files using mpif90 build use
>> gfortran but can't find the magic incantation (it compiles and runs
>> but
>> no logging files produced). mpif90 -mpe=mpilog -echo gives the below.
>>
>> I note that if I use g77 it all works as expected for my trivial
>> example. Unfortunately the code I really wish to use the MPE with
>> is a
>> large F90 code with modules etc which is seems g77 won't cope with.
>>
>> ta. M
>> =# >> + '[' nono ']'
>> + unset 'allargs[0]'
>> ++ expr 0 + 1
>> + argno=1
>> + for arg in '"$@"'
>> + addarg=yes
>> + case "$arg" in
>> ++ echo A-mpe=mpilog
>> ++ sed -e s/A-mpe=//g
>> + profConf=mpilog
>> + profConf=mpe_mpilog
>> + addarg=no
>> + '[' no = no ']'
>> + unset 'allargs[1]'
>> ++ expr 1 + 1
>> + argno=2
>> + for arg in '"$@"'
>> + addarg=yes
>> + case "$arg" in
>> + '[' yes = no ']'
>> ++ expr 2 + 1
>> + argno=3
>> + '[' no = yes ']'
>> + mpilibs='-lmpichf90 -lmpich'
>> + F90FLAGS=' '
>> + LDFLAGS=' '
>> + '[' -n mpe_mpilog ']'
>> + profConffile=
>> + '[' -s /software/64/mpich2-1.0.6/lib/libmpe_mpilog.a -o
>> -s /software/64/mpich2-1.0.6/lib/libmpe_mpilog.so ']'
>> + '[' -s /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf ']'
>> + profConffile=/software/64/mpich2-1.0.6/etc/mpe_mpilog.conf
>> + '[' -n /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf -a
>> -s /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf ']'
>> + . /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf
>> ++ MPE_INCDIR=/software/64/mpich2-1.0.6/include
>> ++ MPE_LIBDIR=/software/64/mpich2-1.0.6/lib
>> ++ MPE_ETCDIR=/software/64/mpich2-1.0.6/etc
>> ++ MPE_LOG_LIBS='-llmpe -lmpe'
>> ++ '[' -n '' -o -n gfortran ']'
>> ++ . /software/64/mpich2-1.0.6/etc/mpe_f77env.conf
>> +++ MPE_FINC_LDR=-I
>> +++ MPE_FINC_LDR=-I
>> +++ MPE_FLIB_LDR=-L
>> +++ MPE_FLIB_LDR=-L
>> +++ MPE_F2CMPI_LIBS=-lmpe_f2cmpi
>> +++ MPE_F2CMPI_LIBS=-lmpe_f2cmpi
>> ++ PROFILE_INCPATHS=-I/software/64/mpich2-1.0.6/include
>> ++ PROFILE_PRELIB='-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -
>> llmpe
>> -lmpe'
>> ++ . /software/64/mpich2-1.0.6/etc/mpe_log_postlib.conf
>> +++ MPE_LOG_THREAD_LIBS=
>> ++ PROFILE_POSTLIB=
>> ++ '[' -f /software/64/mpich2-1.0.6/etc/mpe_callstack_ldflags.conf
>> ']'
>> ++ . /software/64/mpich2-1.0.6/etc/mpe_callstack_ldflags.conf
>> +++ MPE_CALLSTACK_LDFLAGS=-Wl,--export-dynamic
>> +++ '[' * '!=' no -a * '!=' false ']'
>> +++ '[' x-Wl,--export-dynamic '!=' x ']'
>> +++ LDFLAGS=' -Wl,--export-dynamic'
>> + '[' -n -I/software/64/mpich2-1.0.6/include ']'
>> + F90FLAGS='-I/software/64/mpich2-1.0.6/include '
>> + '[' -n '-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -
>> lmpe' ']'
>> + mpilibs='-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -lmpe
>> -lmpichf90 -lmpich'
>> + '[' -n '' ']'
>> + '[' -z -I ']'
>> + F90INCDIRS=-I/software/64/mpich2-1.0.6/include
>> + moduledir=/software/64/mpich2-1.0.6/include
>> + modulelib=mpichf90
>> + '[' -n '' ']'
>> + '[' -n -I ']'
>> + F90MODDIRS=-I/software/64/mpich2-1.0.6/include
>> + F90MODLIBS=-lmpichf90
>> + '[' yes = yes ']'
>> + '[' -n '' ']'
>> + gfortran -I/software/64/mpich2-1.0.6/include -Wl,--export-dynamic
>> pi3f90.f90 -I/software/64/mpich2-1.0.6/include
>> -I/software/64/mpich2-1.0.6/include -L/software/64/mpich2-1.0.6/lib
>> -lmpichf90 -L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -lmpe
>> -lmpichf90 -lmpich -lpthread -lrt
>> + rc=0
>> + '[' -n '' ']'
>> + exit 0
>>
>
>>
>
>>
>> ```
>
> New description:
>
> ```
>
> I'm wishing to use -mpe=mpilog for F90 files using mpif90 build use
> gfortran but can't find the magic incantation (it compiles and runs
> but
> no logging files produced). mpif90 -mpe=mpilog -echo gives the below.
>
> I note that if I use g77 it all works as expected for my trivial
> example. Unfortunately the code I really wish to use the MPE with is a
> large F90 code with modules etc which is seems g77 won't cope with.
>
> ta. M
> =# > + '[' nono ']'
> + unset 'allargs[0]'
> ++ expr 0 + 1
> + argno=1
> + for arg in '"$@"'
> + addarg=yes
> + case "$arg" in
> ++ echo A-mpe=mpilog
> ++ sed -e s/A-mpe=//g
> + profConf=mpilog
> + profConf=mpe_mpilog
> + addarg=no
> + '[' no = no ']'
> + unset 'allargs[1]'
> ++ expr 1 + 1
> + argno=2
> + for arg in '"$@"'
> + addarg=yes
> + case "$arg" in
> + '[' yes = no ']'
> ++ expr 2 + 1
> + argno=3
> + '[' no = yes ']'
> + mpilibs='-lmpichf90 -lmpich'
> + F90FLAGS=' '
> + LDFLAGS=' '
> + '[' -n mpe_mpilog ']'
> + profConffile=
> + '[' -s /software/64/mpich2-1.0.6/lib/libmpe_mpilog.a -o
> -s /software/64/mpich2-1.0.6/lib/libmpe_mpilog.so ']'
> + '[' -s /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf ']'
> + profConffile=/software/64/mpich2-1.0.6/etc/mpe_mpilog.conf
> + '[' -n /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf -a
> -s /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf ']'
> + . /software/64/mpich2-1.0.6/etc/mpe_mpilog.conf
> ++ MPE_INCDIR=/software/64/mpich2-1.0.6/include
> ++ MPE_LIBDIR=/software/64/mpich2-1.0.6/lib
> ++ MPE_ETCDIR=/software/64/mpich2-1.0.6/etc
> ++ MPE_LOG_LIBS='-llmpe -lmpe'
> ++ '[' -n '' -o -n gfortran ']'
> ++ . /software/64/mpich2-1.0.6/etc/mpe_f77env.conf
> +++ MPE_FINC_LDR=-I
> +++ MPE_FINC_LDR=-I
> +++ MPE_FLIB_LDR=-L
> +++ MPE_FLIB_LDR=-L
> +++ MPE_F2CMPI_LIBS=-lmpe_f2cmpi
> +++ MPE_F2CMPI_LIBS=-lmpe_f2cmpi
> ++ PROFILE_INCPATHS=-I/software/64/mpich2-1.0.6/include
> ++ PROFILE_PRELIB='-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe
> -lmpe'
> ++ . /software/64/mpich2-1.0.6/etc/mpe_log_postlib.conf
> +++ MPE_LOG_THREAD_LIBS=
> ++ PROFILE_POSTLIB=
> ++ '[' -f /software/64/mpich2-1.0.6/etc/mpe_callstack_ldflags.conf ']'
> ++ . /software/64/mpich2-1.0.6/etc/mpe_callstack_ldflags.conf
> +++ MPE_CALLSTACK_LDFLAGS=-Wl,--export-dynamic
> +++ '[' * '!=' no -a * '!=' false ']'
> +++ '[' x-Wl,--export-dynamic '!=' x ']'
> +++ LDFLAGS=' -Wl,--export-dynamic'
> + '[' -n -I/software/64/mpich2-1.0.6/include ']'
> + F90FLAGS='-I/software/64/mpich2-1.0.6/include '
> + '[' -n '-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -lmpe'
> ']'
> + mpilibs='-L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -lmpe
> -lmpichf90 -lmpich'
> + '[' -n '' ']'
> + '[' -z -I ']'
> + F90INCDIRS=-I/software/64/mpich2-1.0.6/include
> + moduledir=/software/64/mpich2-1.0.6/include
> + modulelib=mpichf90
> + '[' -n '' ']'
> + '[' -n -I ']'
> + F90MODDIRS=-I/software/64/mpich2-1.0.6/include
> + F90MODLIBS=-lmpichf90
> + '[' yes = yes ']'
> + '[' -n '' ']'
> + gfortran -I/software/64/mpich2-1.0.6/include -Wl,--export-dynamic
> pi3f90.f90 -I/software/64/mpich2-1.0.6/include
> -I/software/64/mpich2-1.0.6/include -L/software/64/mpich2-1.0.6/lib
> -lmpichf90 -L/software/64/mpich2-1.0.6/lib -lmpe_f2cmpi -llmpe -lmpe
> -lmpichf90 -lmpich -lpthread -lrt
> + rc=0
> + '[' -n '' ']'
> + exit 0
>
>
>
>
>
> ```
>
> --
>
> Comment:
>
> resolving this for now until we hear more from the user.
>
> --
> Ticket URL: <http://trac.mcs.anl.gov/projects/mpich2/ticket/721#comment:8
> >
> mpich2 <http://trac.mcs.anl.gov/projects/mpich2>
>
}}}Originally by chan on 2009-07-27 11:16:49 -0500
Michael,
I actually don't know what causes -mpe=mpilog failed with mpif90 in your case. It is likely the mpich2-1.0.6p1 has a bug in mpif90 or even configure that causes your compiler combination F77=g77 and F90=ifort failed. The best way to debug the problem is for you to configure/build a new version of mpich2 (the latest is now 1.1.1) using F77=ifort and F90=ifort and see if the problem goes away. If not, we could debug from there.
A.Chan
Replying to michael.bane@…:
was there no way to just use the flags to over-ride and use correct lib/lib paths? ta, M
mpichbot
commented
8 years ago Originally by michael.bane@manchester.ac.uk on 2009-07-27 12:01:53 -0500
> Michael,
>
> I actually don't know what causes -mpe=mpilog failed with mpif90 in
> your
> case.
> It is likely the mpich2-1.0.6p1 has a bug in mpif90 or even
> configure that
> causes your compiler combination F77=g77 and F90=ifort failed. The
> best
> way
> to debug the problem is for you to configure/build a new version of
> mpich2
> (the latest is now 1.1.1) using F77=ifort and F90=ifort and see if the
> problem
> goes away. If not, we could debug from there.
>
> A.Chan
Sir, thanks for explaining! Unfort I'm not sys admin on this sys so
will have to give the above a miss. Therefore pls close this call.
Ta, Michael
Originally by chan on 2009-07-27 12:40:31 -0500
Michael,
You don't need to be a sysadm to install mpich2. You can do "configure/make/make install" all as a regular user and install mpich2 in your home directory. Just follow the README. The only thing you need add in your configure command is "F77=ifort F90=ifort", e.g. "configure F77=ifort F90=ifort --prefix=$HOME/mpich2-111". where install directory becomes $HOME/mpich2-111. Then just invoke the full path, $HOME/mpich2-111/bin/mpif90, in your compile command (or in your Makefile) to compile/link your fortran90 app.
A.Chan
mpichbot
commented
8 years ago Originally by chan on 2009-07-30 12:49:38 -0500
resolved until we hear more from user.
Originally by michael michael.bane@manchester.ac.uk on 2009-07-13 16:29:19 -0500