<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi<br>
<br>
I have noticed problems in running Fortran MPICH2 applications.
Basically, the prints to standard output from a Fortran module don't
seem to work properly. They appear after the program has exited.
This problem doesn't exist with C program.<br>
<br>
I did a test with "fpi.f" example. I have used MPICH2-1.3.3rc1 and
mingw-w64-1.0-bin_i686-mingw_20101129 compiler. (I have tested it
with GCC 4.5.2 provided by <a class="moz-txt-link-abbreviated" href="http://www.equation.com">www.equation.com</a> and the results are
same.) Below are screen shots when I run fpi.exe using mpiexec and
then directly:<br>
<br>
<hr size="2" width="100%">C:\tmp\mpi><b><font color="#ff0000">"C:\Program
Files\MPICH2\bin"\mpiexec.exe -n 1 -localonly fpi.exe</font></b><br>
<br>
9<br>
12<br>
0<br>
Process 0 of 1 is alive<br>
Enter the number of intervals: (0 quits)<br>
pi is approximately: 3.1426214565576127 Error is:
0.0010288029678196<br>
Enter the number of intervals: (0 quits)<br>
pi is approximately: 3.1421713566497975 Error is:
0.0005787030600044<br>
Enter the number of intervals: (0 quits)<br>
<hr size="2" width="100%">C:\tmp\mpi><b><font color="#ff0000">fpi.exe</font></b><br>
Process 0 of 1 is alive<br>
Enter the number of intervals: (0 quits)<br>
9<br>
pi is approximately: 3.1426214565576127 Error is:
0.0010288029678196<br>
Enter the number of intervals: (0 quits)<br>
0<br>
<br>
C:\tmp\mpi><br>
<hr size="2" width="100%"><br>
I did not find any options for mpiexec to overcome this. Thanks for
your help.<br>
<br>
Best Regards<br>
Arun<br>
<br>
<br>
On 23-02-2011 10:14, Arun Murthy wrote:
<blockquote cite="mid:4D6490B2.5090001@fluidyn.com" type="cite">Hi
Jayesh
<br>
<br>
Thanks for your answer. For the moment, I will continue to work
with GCC V4.5.x.
<br>
<br>
But, this raises one doubt in my mind. Perhaps, this is not the
right forum to raise this question. Nevertheless, I am counting on
the experience and knowledge of people at ANL and on this forum.
What happens when I migrate to a new GCC compiler, say V4.7 or
V4.8 or even V5. Will there be a backward compatibility with the
MPICH2 libraries or will I have to rebuild MPICH2 on the new
compiler suite? I have encountered several such backward
compatibility problems with GCC on Linux.
<br>
<br>
Thanks for your answers
<br>
<br>
Best Regards
<br>
Arun
<br>
<br>
<br>
<br>
On 22-02-2011 22:27, Jayesh Krishna wrote:
<br>
<blockquote type="cite">Hi,
<br>
It is possible that mingw gcc version 4.4.3 is old (64-bit was
in the nascent stage) and does not support 64-bit libs generated
from Windows libraries. I test libmpi.a using mingw gcc version
4.6.0 .
<br>
<br>
Regards,
<br>
Jayesh
<br>
<br>
----- Original Message -----
<br>
From: "Arun Murthy"<a class="moz-txt-link-rfc2396E" href="mailto:arun.murthy@fluidyn.com"><arun.murthy@fluidyn.com></a>
<br>
To: "Jayesh Krishna"<a class="moz-txt-link-rfc2396E" href="mailto:jayesh@mcs.anl.gov"><jayesh@mcs.anl.gov></a>
<br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
Sent: Tuesday, February 22, 2011 9:31:21 AM
<br>
Subject: Re: [mpich-discuss] MPICH2 On Windows 64 bit and
Mingw-w64 compilers
<br>
<br>
Hi Jayesh
<br>
<br>
I am linking with libmpi.a. I am able to run the code after
compiling it
<br>
with V4.5.3.
<br>
<br>
With Best Regards
<br>
Arun
<br>
<br>
<br>
On 22-02-2011 20:55, Jayesh Krishna wrote:
<br>
<blockquote type="cite">Hi,
<br>
Are you linking using libmpi.a or mpi.lib ? Are you able to
run your code after compiling it with V4.5.3 ?
<br>
<br>
Regards,
<br>
Jayesh
<br>
<br>
----- Original Message -----
<br>
From: "Arun Murthy"<a class="moz-txt-link-rfc2396E" href="mailto:arun.murthy@fluidyn.com"><arun.murthy@fluidyn.com></a>
<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
Sent: Tuesday, February 22, 2011 7:05:51 AM
<br>
Subject: Re: [mpich-discuss] MPICH2 On Windows 64 bit and
Mingw-w64 compilers
<br>
<br>
<br>
Hi
<br>
<br>
I downloaded the MPICH2-1.3.2p1 Windows EM64T/AMD64 (binary)
onto my Windows-XP 64bit machine. I tried to use it with two
GNU compilers: V4.4.3 and V.4.5.3. Basically, I tried to link
the icpi.c example into an executable. With GCC V4.4.3, I get
undefined symbols, while with V4.5.3, it works well. Does it
mean that, if I want to use GCC V4.4.3, I need to rebuild
MPICH2 from the source using the V4.4.3 compiler?
<br>
<br>
The output details of my trials are below.
<br>
<br>
Thanks for your help.
<br>
<br>
With Best Regards
<br>
Arun
<br>
<br>
D:\tmp>"C:\Program Files\mingw_443\64bit\bin\gcc.exe" --ver
<br>
<br>
Built by Equation Solution<a class="moz-txt-link-rfc2396E" href="http://www.Equation.com"><http://www.Equation.com></a> .
<br>
Using built-in specs.
<br>
Target: x86_64-pc-mingw32
<br>
Configured with: ../gcc-4.4.3-mingw/configure
--host=x86_64-pc-mingw32 --build=x86_64-unknown-linux-gnu
--target=x86_64-pc-mingw32
--prefix=/home/gfortran/gcc-home/binary/mingw32/native/x86_64/gcc/4.4.3
--with-gmp=/home/gfortran/gcc-home/binary/mingw32/native/x86_64/gmp
--with-mpfr=/home/gfortran/gcc-home/binary/mingw32/native/x86_64/mpfr
--with-mpc=/home/gfortran/gcc-home/binary/mingw32/native/x86_64/mpc
--with-sysroot=/home/gfortran/gcc-home/binary/mingw32/cross/x86_64/gcc/4.4.3
--with-gcc --with-gnu-ld --with-gnu-as --disable-shared
--disable-nls --disable-tls --enable-libgomp
--enable-languages=c,fortran,c++ --enable-threads=win32
--disable-win32-registry
<br>
Thread model: win32
<br>
gcc version 4.4.3 (GCC)
<br>
<br>
D:\tmp>"C:\Program Files\mingw_443\64bit\bin\gcc.exe"
-I"C:\Program Files\MPICH2\include" icpi.c -L"C:\Program
Files\MPICH2"\lib -lmpi -o icpi.exe
<br>
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x76):
undefined reference to `MPI_Init'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x87):
undefined reference to `MPI_Comm_size'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x98):
undefined reference to `MPI_Comm_rank'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0xab):
undefined reference to `MPI_Get_processor_name'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x142):
undefined reference to `MPI_Wtime'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x16c):
undefined reference to `MPI_Bcast'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x237):
undefined reference to `MPI_Reduce'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x2b4):
undefined reference to `MPI_Wtime'
<br>
C:\DOCUME~1\ns\LOCALS~1\Temp\ccg2hczk.o:icpi.c:(.text+0x31b):
undefined reference to `MPI_Finalize'
<br>
collect2: ld returned 1 exit status
<br>
<br>
D:\tmp>"C:\Program
Files\mingw-w64\bin\x86_64-w64-mingw32-gcc.exe" --ver
<br>
<br>
Using built-in specs.
<br>
COLLECT_GCC=C:\Program
Files\mingw-w64\bin\x86_64-w64-mingw32-gcc.exe
<br>
COLLECT_LTO_WRAPPER=c:/program
files/mingw-w64/bin/../libexec/gcc/x86_64-w64-min
<br>
gw32/4.5.3/lto-wrapper.exe
<br>
Target: x86_64-w64-mingw32
<br>
Configured with: ../../../build/gcc/src/configure
--target=x86_64-w64-mingw32
--prefix=/c/buildbot/mingw-w64/mingw32/mingw-x86-x86_64/build/build/root
--with-sysroot=/c/buildbot/mingw-w64/mingw32/mingw-x86-x86_64/build/build/root
--enable-languages=all,obj-c++ --enable-fully-dynamic-string
--disable-multilib
<br>
Thread model: win32
<br>
gcc version 4.5.3 20110207 (prerelease) (GCC)
<br>
<br>
D:\tmp>"C:\Program
Files\mingw-w64\bin\x86_64-w64-mingw32-gcc.exe" -I"C:\Program
Files\MPICH2\include" icpi.c -L"C:\Program Files\MPICH2"\lib
-lmpi -lfmpich2g -
<br>
o icpi.exe
<br>
<br>
SUCCESS
<br>
<br>
D:\tmp>
<br>
<br>
<br>
On 11-01-2011 18:53, Arun Murthy wrote:
<br>
<br>
Hi Jayesh
<br>
<br>
Yes, I linked icpi.o with mpi.lib. Happy to hear that Mingw64
support will be available this month. I can wait for a couple
of weeks for the next release. In the meantime, if you want me
to test the pre-release version, I would be happy to do that.
<br>
<br>
Thanks for your help.
<br>
<br>
Best regards
<br>
Arun
<br>
<br>
<br>
On 11-01-2011 17:10, Jayesh Krishna wrote:
<br>
<br>
<br>
Hi,
<br>
Are you trying to link your code with mpi.lib ? Mingw
compilers may not be playing nice with the windows libraries.
AFAICT we added support for mingw 64-bit compilers (*.a
libraries compatible with mingw 64-bit compilers) after 1.3.1
was released. It should be available in the next release,
1.3.2, due this month.
<br>
<br>
(PS: If you need it sooner than that let me know and I can get
you a custom build for development purposes)
<br>
Regards,
<br>
Jayesh
<br>
<br>
----- Original Message -----
<br>
From: "Arun Murthy"<a class="moz-txt-link-rfc2396E" href="mailto:arun.murthy@fluidyn.com"><arun.murthy@fluidyn.com></a>
<br>
To: "Jayesh Krishna"<a class="moz-txt-link-rfc2396E" href="mailto:jayesh@mcs.anl.gov"><jayesh@mcs.anl.gov></a>
<br>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
Sent: Tuesday, January 11, 2011 2:12:01 AM
<br>
Subject: Re: [mpich-discuss] MPICH2 On Windows 64 bit and
Mingw-w64 compilers
<br>
<br>
Hi Jayesh
<br>
<br>
I opened CMD with "Run as administrator" and did the
following:
<br>
<br>
C:\tmp>"C:\Program Files\MPICH2\bin"\mpiexec.exe -n 2
-localroot c:\tmp\icpi.exe
<br>
<br>
Job terminated with following error message:
<br>
<br>
"
<br>
Error posting writev, A request to send or receive data was
disallowed because the socket had already been shut down in
that direction with a previous shutdown call.(10058)
<br>
unable to post a write for the next command,
<br>
sock error: Error = 10058
<br>
<br>
unable to post a write of the closed_request command to the
parent context.
<br>
unable to close the stdin context.
<br>
state machine failed.
<br>
"
<br>
<br>
C:\tmp>"C:\Program Files\MPICH2\bin"\mpiexec.exe -n 2
-localroot -exitcodes c:\tmp\icpi.exe
<br>
<br>
Job terminated with following error message:
<br>
<br>
"
<br>
rank: node: exit code
<br>
0: Arun-PC: -1073741819
<br>
1: Arun-PC: -1073741819
<br>
"
<br>
<br>
C:\tmp>"C:\Program Files\MPICH2\bin"\smpd -status
<br>
<br>
"
<br>
smpd running on Arun-PC
<br>
"
<br>
<br>
Thanks for your help.
<br>
Best Regards
<br>
Arun
<br>
On 10-01-2011 22:08, Jayesh Krishna wrote:
<br>
<br>
Hi,
<br>
Can you try running the job from an administrator command
prompt (Note that opening a command prompt from an
administrator account does not give you an admin command
prompt. Right-click on the command prompt icon and select "Run
as administrator" to get an admin command prompt) and see if
it works ?
<br>
Can you also check the status of the MPICH2 process manager
(Type "smpd -status" at the command prompt)?
<br>
<br>
Regards,
<br>
Jayesh
<br>
----- Original Message -----
<br>
From: Arun Murthy<a class="moz-txt-link-rfc2396E" href="mailto:arun.murthy@fluidyn.com"><arun.murthy@fluidyn.com></a> To: Jayesh
Krishna<a class="moz-txt-link-rfc2396E" href="mailto:jayesh@mcs.anl.gov"><jayesh@mcs.anl.gov></a> Cc:
<a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a> Sent: Mon, 10 Jan 2011 01:33:41
-0600 (CST)
<br>
Subject: Re: [mpich-discuss] MPICH2 On Windows 64 bit and
Mingw-w64 compilers
<br>
<br>
Hi Jayesh
<br>
<br>
I tried that. It did not help. Here is the response:
<br>
<br>
"
<br>
C:\tmp>"C:\Program Files\MPICH2\bin"\mpiexec.exe -n 2
-localroot icpi.exe
<br>
<br>
Unable to open the
HKEY_LOCAL_MACHINE\SOFTWARE\MPICH\SMPD\process\6308
<br>
registry key, error 5, Access is denied.
<br>
Unable to open the
HKEY_LOCAL_MACHINE\SOFTWARE\MPICH\SMPD\process\808
<br>
registry k ey, error 5, Access is denied.
<br>
"
<br>
<br>
When I killed the job by<CTRL> C, the following
messages appeared:
<br>
<br>
"
<br>
mpiexec aborting job...
<br>
received suspend command for a pmi context that doesn't exist:
unmatched
<br>
id = 1
<br>
<br>
job aborted:
<br>
rank: node: exit code[: error message]
<br>
0: Arun-PC: -1073741819: mpiexec aborting job
<br>
1: Arun-PC: -1073741819
<br>
Terminate batch job (Y/N)? y
<br>
"
<br>
<br>
When I tried the same thing on the pre-built "cpi.exe", I get
the same
<br>
messages that I got with "icpi.exe", but it still works:
<br>
<br>
"
<br>
C:\tmp>"C:\Program Files\MPICH2\bin"\mpiexec.exe -n 2
-localroot cpi
<br>
<br>
Unable to open the
HKEY_LOCAL_MACHINE\SOFTWARE\MPICH\SMPD\process\4544
<br>
registry key, error 5, Access is denied.
<br>
Unable to open the
HKEY_LOCAL_MACHINE\SOFTWARE\MPICH\SMPD\process\7288
<br>
registry key, error 5, Access is denied.
<br>
<br>
Enter the number of intervals: (0 quits) 9
<br>
pi is approximately 3.1426214565576127, Error is
0.0010288029678196
<br>
wall clock time = 0.000077
<br>
<br>
Enter the number of intervals: (0 quits)
<br>
"
<br>
<br>
When I killed this job by<CTRL> C, the following
messages appeared:
<br>
<br>
"
<br>
mpiexec aborting job...
<br>
SuspendThread failed with error 5 for process
<br>
0:33FB034C-A281-4d45-9189-9DDCDC33C941:'cpi'
<br>
unable to suspend process.
<br>
unable to read the cmd header on the pmi context, Error = -1.
<br>
Error posting readv, An existing connection was forcibly
closed by the
<br>
remote host.(10054)
<br>
<br>
SuspendThread failed with error 5 for process
<br>
1:33FB034C-A281-4d45-9189-9DDCDC33C941:'cpi'
<br>
unable to suspend process.
<br>
unable to read the cmd header on the pmi context, Error = -1.
<br>
Error posting readv, An existing connection was forcibly
closed by the
<br>
remote host.(10054)
<br>
<br>
received kill command for a pmi context that doesn't exist:
unmatched id = 0
<br>
<br>
job aborted:
<br>
rank: node: exit code[: error message]
<br>
0: Arun-PC: 123: process 0 exited without calling finalize
<br>
1: Arun-PC: 123: process 1 exited without calling finalize
<br>
Terminate batch job (Y/N)? y
<br>
"
<br>
<br>
Does it have anything to do with an incorrect node
(-1073741819) on
<br>
which mpiexec is trying to launch the processes? Thanks for
your help.
<br>
<br>
Best Regards
<br>
Arun
<br>
<br>
<br>
On 07-01-2011 22:11, Jayesh Krishna wrote:
<br>
<br>
Hi,
<br>
Can you try running your program with the "-localroot" option
and let us know if it works for you (mpiexec -n 2 -localroot
icpi.exe)?
<br>
<br>
Regards,
<br>
Jayesh
<br>
<br>
----- Original Message -----
<br>
From: "Arun Murthy"<a class="moz-txt-link-rfc2396E" href="mailto:arun.murthy@fluidyn.com"><arun.murthy@fluidyn.com></a> To:
<a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a> Sent: Friday, January 7, 2011
12:56:17 AM
<br>
Subject: [mpich-discuss] MPICH2 On Windows 64 bit and
Mingw-w64 compilers
<br>
<br>
Hi
<br>
<br>
I am trying to use MPICH2 on Windows 7 64bit (installed from
<br>
mpich2-1.3.1-win-x86-64.msi) along with Mingw-w64 compiler
suite
<br>
(mingw-w64-1.0-bin_i686-mingw_20101129).
<br>
<br>
I tried to compile-link the example "icpi.c" using following
command:
<br>
<br>
C:\MinGW\mingw-w64-1.0-bin_i686-mingw_20101129\bin\x86_64-w64-mingw32-gcc.exe
<br>
-I"C:\Program Files\MPICH2\include" icpi.c -L"C:\Program
<br>
Files\MPICH2\lib" -lmpi -o icpi.exe
<br>
<br>
I could get the executable, but it doesn't run with any number
of
<br>
processors. When run with mpiexec, it aborts without any
message. I
<br>
could run the pre-built "cpi.exe" with any number of CPU's. I
don't have
<br>
MS Visual Studio on my machine. Can anyone help?
<br>
<br>
By the way, the 32-bit version of MPICH1 (1.2.5 SDK.gcc) works
well with
<br>
Mingw-w32 compiler suite.
<br>
<br>
Thanks
<br>
Arun
<br>
<br>
<br>
_______________________________________________
<br>
mpich-discuss mailing list <a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<a class="moz-txt-link-freetext" href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a>
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
mpich-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a>
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
mpich-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
mpich-discuss mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mpich-discuss@mcs.anl.gov">mpich-discuss@mcs.anl.gov</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a>
<br>
<br>
<br>
<br>
</blockquote>
</body>
</html>