April 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] cross compiling using mpich
by Jeff Hammond 16 Apr '15

16 Apr '15

On Thursday, April 16, 2015, Jeff Hammond <jeff.science(a)gmail.com> wrote: > > > On Thursday, April 16, 2015, Rob Latham <robl(a)mcs.anl.gov > <javascript:_e(%7B%7D,'cvml','robl(a)mcs.anl.gov');>> wrote: > >> >> >> On 04/16/2015 08:33 AM, Jeff Hammond wrote: >> >>> https://wiki.mpich.org/mpich/index.php/Frequently_Asked_ >>> Questions#Q:_Why_can.27t_I_build_MPICH_on_Windows_anymore.3F >>> >>> >> well jeff since you unhelpfully replied to this poor guy with a link to >> the wiki that he already got last week, allow me to be pedantic for a >> moment: he's not building mpich *on* windows. he's building mpich *for* >> windows. *On* linux. >> >> > Is the FAQ precise that building on Windows is the problem, as opposed to > building for Windows? Because I have to believe the issues cannot be > separated. What compiler executes on Linux that can generate Windows > executables? That doesn't even seem remotely feasible, particularly if any > header in MPICH is included from a sub directory, since the slashes will be > wrong on a Linux file system. > > I stand by my redundant response unless someone can explain the theory of > how it would work. > I suck. Here it is: http://www.blogcompiler.com/2010/07/11/compile-for-windows-on-linux/ Jeff > > Jeff > > >> >> >> >> On Wed, Apr 15, 2015 at 12:37 AM, mapalo92 . <mapalo2008(a)gmail.com> >>> wrote: >>> >>>> my target is windows and my host is linux >>>> >>>> 2015-04-09 17:07 GMT+03:00 Rob Latham <robl(a)mcs.anl.gov>: >>>> >>>>> >>>>> >>>>> >>>>> On 04/09/2015 03:33 AM, mapalo92 . wrote: >>>>> >>>>>> >>>>>> Is possible to use mpich in order to cross compile between windows and >>>>>> linux? I tried to built mpich 's libraries using mingw-w64 but nothing >>>>>> done. I got many many errors. Any feedback will be helpful. >>>>>> >>>>> >>>>> >>>>> which is your target and which is your host? If you are building a >>>>> linux >>>>> target on a windows host, you might be better off setting up a virtual >>>>> machine and doing your cross compilation there. >>>>> >>>>> In general, cross compilation works with mpich: we do it regularly for >>>>> Blue Gene. >>>>> >>>>> ==rob >>>>> >>>>> -- >>>>> Rob Latham >>>>> Mathematics and Computer Science Division >>>>> Argonne National Lab, IL USA >>>>> >>>>> _______________________________________________ >>>>> discuss mailing list discuss(a)mpich.org >>>>> To manage subscription options or unsubscribe: >>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> >>> >>> >>> >>> >> -- >> Rob Latham >> Mathematics and Computer Science Division >> Argonne National Lab, IL USA >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > > -- > Jeff Hammond > jeff.science(a)gmail.com > <javascript:_e(%7B%7D,'cvml','jeff.science(a)gmail.com');> > http://jeffhammond.github.io/ > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] cross compiling using mpich
by Jeff Hammond 16 Apr '15

16 Apr '15

On Thursday, April 16, 2015, Rob Latham <robl(a)mcs.anl.gov> wrote: > > > On 04/16/2015 08:33 AM, Jeff Hammond wrote: > >> https://wiki.mpich.org/mpich/index.php/Frequently_Asked_ >> Questions#Q:_Why_can.27t_I_build_MPICH_on_Windows_anymore.3F >> >> > well jeff since you unhelpfully replied to this poor guy with a link to > the wiki that he already got last week, allow me to be pedantic for a > moment: he's not building mpich *on* windows. he's building mpich *for* > windows. *On* linux. > > Is the FAQ precise that building on Windows is the problem, as opposed to building for Windows? Because I have to believe the issues cannot be separated. What compiler executes on Linux that can generate Windows executables? That doesn't even seem remotely feasible, particularly if any header in MPICH is included from a sub directory, since the slashes will be wrong on a Linux file system. I stand by my redundant response unless someone can explain the theory of how it would work. Jeff > > > > On Wed, Apr 15, 2015 at 12:37 AM, mapalo92 . <mapalo2008(a)gmail.com> >> wrote: >> >>> my target is windows and my host is linux >>> >>> 2015-04-09 17:07 GMT+03:00 Rob Latham <robl(a)mcs.anl.gov>: >>> >>>> >>>> >>>> >>>> On 04/09/2015 03:33 AM, mapalo92 . wrote: >>>> >>>>> >>>>> Is possible to use mpich in order to cross compile between windows and >>>>> linux? I tried to built mpich 's libraries using mingw-w64 but nothing >>>>> done. I got many many errors. Any feedback will be helpful. >>>>> >>>> >>>> >>>> which is your target and which is your host? If you are building a linux >>>> target on a windows host, you might be better off setting up a virtual >>>> machine and doing your cross compilation there. >>>> >>>> In general, cross compilation works with mpich: we do it regularly for >>>> Blue Gene. >>>> >>>> ==rob >>>> >>>> -- >>>> Rob Latham >>>> Mathematics and Computer Science Division >>>> Argonne National Lab, IL USA >>>> >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> >>> >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >> >> >> >> > -- > Rob Latham > Mathematics and Computer Science Division > Argonne National Lab, IL USA > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] cross compiling using mpich
by Rob Latham 16 Apr '15

16 Apr '15

On 04/16/2015 08:33 AM, Jeff Hammond wrote: > https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_ca… > well jeff since you unhelpfully replied to this poor guy with a link to the wiki that he already got last week, allow me to be pedantic for a moment: he's not building mpich *on* windows. he's building mpich *for* windows. *On* linux. None of us have ever done that, though, so mapalo92 is on his/her own. ==rob > On Wed, Apr 15, 2015 at 12:37 AM, mapalo92 . <mapalo2008(a)gmail.com> wrote: >> my target is windows and my host is linux >> >> 2015-04-09 17:07 GMT+03:00 Rob Latham <robl(a)mcs.anl.gov>: >>> >>> >>> >>> On 04/09/2015 03:33 AM, mapalo92 . wrote: >>>> >>>> Is possible to use mpich in order to cross compile between windows and >>>> linux? I tried to built mpich 's libraries using mingw-w64 but nothing >>>> done. I got many many errors. Any feedback will be helpful. >>> >>> >>> which is your target and which is your host? If you are building a linux >>> target on a windows host, you might be better off setting up a virtual >>> machine and doing your cross compilation there. >>> >>> In general, cross compilation works with mpich: we do it regularly for >>> Blue Gene. >>> >>> ==rob >>> >>> -- >>> Rob Latham >>> Mathematics and Computer Science Division >>> Argonne National Lab, IL USA >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] cross compiling using mpich
by Jeff Hammond 16 Apr '15

16 Apr '15

https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_ca… On Wed, Apr 15, 2015 at 12:37 AM, mapalo92 . <mapalo2008(a)gmail.com> wrote: > my target is windows and my host is linux > > 2015-04-09 17:07 GMT+03:00 Rob Latham <robl(a)mcs.anl.gov>: >> >> >> >> On 04/09/2015 03:33 AM, mapalo92 . wrote: >>> >>> Is possible to use mpich in order to cross compile between windows and >>> linux? I tried to built mpich 's libraries using mingw-w64 but nothing >>> done. I got many many errors. Any feedback will be helpful. >> >> >> which is your target and which is your host? If you are building a linux >> target on a windows host, you might be better off setting up a virtual >> machine and doing your cross compilation there. >> >> In general, cross compilation works with mpich: we do it regularly for >> Blue Gene. >> >> ==rob >> >> -- >> Rob Latham >> Mathematics and Computer Science Division >> Argonne National Lab, IL USA >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] How many ports for MPIEXEC_PORT_RANGE?
by Huiwei Lu 15 Apr '15

15 Apr '15

Hi Josef, I am not familiar with MPICH_PORT_RANGE but I think you can experiment how many ports does each process need. For starters, you can probably estimate a minimum of 6 ports per process. There was an old post about MPICH_PORT_RANGE but I think the suggestion is still valid today. http://lists.mcs.anl.gov/pipermail/mpich-discuss/2006-July/001485.html Best regards, -- Huiwei On Tue, Apr 14, 2015 at 6:11 AM, HEINZ Josef (AREVA) <josef.heinz(a)areva.com> wrote: > Hello together, > > > > I have to restrict the port range with MPIEXEC _PORT_RANGE. Does anyone > know how many ports are necessary to establish a communication between two > hosts? On host1 only one process and on host2 two processes are running. > > > > Thank you very much. > > > > Best regards > > > > Josef > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] cross compiling using mpich
by mapalo92 . 15 Apr '15

15 Apr '15

my target is windows and my host is linux 2015-04-09 17:07 GMT+03:00 Rob Latham <robl(a)mcs.anl.gov>: > > > On 04/09/2015 03:33 AM, mapalo92 . wrote: > >> Is possible to use mpich in order to cross compile between windows and >> linux? I tried to built mpich 's libraries using mingw-w64 but nothing >> done. I got many many errors. Any feedback will be helpful. >> > > which is your target and which is your host? If you are building a linux > target on a windows host, you might be better off setting up a virtual > machine and doing your cross compilation there. > > In general, cross compilation works with mpich: we do it regularly for > Blue Gene. > > ==rob > > -- > Rob Latham > Mathematics and Computer Science Division > Argonne National Lab, IL USA > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

How many ports for MPIEXEC_PORT_RANGE?
by HEINZ Josef (AREVA) 14 Apr '15

14 Apr '15

Hello together, I have to restrict the port range with MPIEXEC _PORT_RANGE. Does anyone know how many ports are necessary to establish a communication between two hosts? On host1 only one process and on host2 two processes are running. Thank you very much. Best regards Josef

1 0

Re: [mpich-discuss] configuration issues: complex.h and CROSS_F77_SIZEOF_INTEGER
by Junchao Zhang 10 Apr '15

10 Apr '15

I think the warnings reported by suncc are harmless. It is probably because the inline asm statements use GNU syntax, and there is a ";;" in a struct after macro expansion. --Junchao Zhang On Fri, Apr 10, 2015 at 1:19 PM, Lou Picciano <LouPicciano(a)comcast.net> wrote: > Thank You, Junchao, > > Spot on! (Duh! Dumb error) > > Am now getting successful(?) compiles to completion, but I see many, many > repetitions of messages like this - for a series of .lo objects: > > Anything to be concerned with? > > CC src/mpid/common/thread/lib_libmpi_la-mpid_thread.lo > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 95: warning: parameter in inline asm statement unused: %2 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 103: warning: parameter in inline asm statement unused: %1 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 111: warning: parameter in inline asm statement unused: %1 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 121: warning: parameter in inline asm statement unused: %2 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 129: warning: parameter in inline asm statement unused: %3 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 142: warning: parameter in inline asm statement unused: %1 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 151: warning: parameter in inline asm statement unused: %1 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 159: warning: parameter in inline asm statement unused: %3 > > "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", > line 167: warning: parameter in inline asm statement unused: %3 > > "src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 156: > warning: syntax error: empty member declaration > "src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 161: > warning: syntax error: > > > > On Apr 9, 2015, at 6:25 PM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > > Lou, > I looked at your config.log. You passed > CC=/opt/solarisstudio12.4/bin/CC to configure, which is wrong. You should > use CC=/opt/solarisstudio12.4/bin/cc. If you want C++, just use CXX=... > > > --Junchao Zhang > > On Thu, Apr 9, 2015 at 9:12 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > I happened to build MPICH with SolarisStudio12.4 for Linux a couple of > days ago. > Could you send config.log of your build? > > --Junchao Zhang > > On Wed, Apr 8, 2015 at 10:51 PM, Lou Cetinich <loucetinich(a)gmail.com > > wrote: > I only need Fortran. > > (In fact, apart from exhaustive testing, and the endpoint target of a > production build), I’d otherwise be happy to disable everything else… (!) > > Lou > > > On Apr 8, 2015, at 11:47 PM, Thakur, Rajeev <thakur(a)mcs.anl.gov> wrote: > > If you don't need to use Fortran, you can configure with --disable-fortran. > > Rajeev > > On Apr 8, 2015, at 10:36 PM, Lou Picciano <loupicciano(a)comcast.net> wrote: > > Attempting to configure mpich-3.2b1 for the SolarisStudio12.4 suite... > > Issues around complex.h (Yes, I'll have to look for prerequisites) > > and the message about FORTRAN integer length - which seems to have been > dealt with a couple of years ago, and only in the ifort context? > > CROSS_F77_SIZEOF_INTEGER seems to be ignored; I've tried all of 1,2,4,8... > > Many thanks! > > checking complex.h presence... yes > configure: WARNING: complex.h: present but cannot be compiled > configure: WARNING: complex.h: check for missing prerequisite headers? > configure: WARNING: complex.h: see the Autoconf documentation > configure: WARNING: complex.h: section "Present But Cannot Be Compiled" > configure: WARNING: complex.h: proceeding with the compiler's result > configure: WARNING: ## -------------------------------- ## > configure: WARNING: ## Report this to discuss(a)mpich.org ## > configure: WARNING: ## -------------------------------- ## > checking for complex.h... no > checking size of _Bool... 0 > checking size of float _Complex... 0 > checking size of double _Complex... 0 > checking size of long double _Complex... 0 > checking for _Bool... no > checking for float _Complex... no > checking for double _Complex... no > checking for long double _Complex... no > checking for size of Fortran type integer... 0 > checking for size of Fortran type real... 0 > checking for size of Fortran type double precision... 0 > checking whether integer*1 is supported... yes > checking whether integer*2 is supported... yes > checking whether integer*4 is supported... yes > checking whether integer*8 is supported... yes > checking whether integer*16 is supported... no > checking whether real*4 is supported... yes > checking whether real*8 is supported... yes > checking whether real*16 is supported... yes > configure: error: Unable to configure with Fortran support because > configure could not determine the size of a Fortran INTEGER. > Consider setting CROSS_F77_SIZEOF_INTEGER to the length in bytes of a > Fortran INTEGER > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] configuration issues: complex.h and CROSS_F77_SIZEOF_INTEGER
by Lou Picciano 10 Apr '15

10 Apr '15

Thank You, Junchao, Spot on! (Duh! Dumb error) Am now getting successful(?) compiles to completion, but I see many, many repetitions of messages like this - for a series of .lo objects: Anything to be concerned with? CC src/mpid/common/thread/lib_libmpi_la-mpid_thread.lo "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 95: warning: parameter in inline asm statement unused: %2 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 103: warning: parameter in inline asm statement unused: %1 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 111: warning: parameter in inline asm statement unused: %1 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 121: warning: parameter in inline asm statement unused: %2 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 129: warning: parameter in inline asm statement unused: %3 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 142: warning: parameter in inline asm statement unused: %1 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 151: warning: parameter in inline asm statement unused: %1 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 159: warning: parameter in inline asm statement unused: %3 "/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 167: warning: parameter in inline asm statement unused: %3 "src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 156: warning: syntax error: empty member declaration "src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 161: warning: syntax error: On Apr 9, 2015, at 6:25 PM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > Lou, > I looked at your config.log. You passed CC=/opt/solarisstudio12.4/bin/CC to configure, which is wrong. You should use CC=/opt/solarisstudio12.4/bin/cc. If you want C++, just use CXX=... > > > --Junchao Zhang > > On Thu, Apr 9, 2015 at 9:12 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > I happened to build MPICH with SolarisStudio12.4 for Linux a couple of days ago. > Could you send config.log of your build? > > --Junchao Zhang > > On Wed, Apr 8, 2015 at 10:51 PM, Lou Cetinich <loucetinich(a)gmail.com> wrote: > I only need Fortran. > > (In fact, apart from exhaustive testing, and the endpoint target of a production build), I’d otherwise be happy to disable everything else… (!) > > Lou > > > On Apr 8, 2015, at 11:47 PM, Thakur, Rajeev <thakur(a)mcs.anl.gov> wrote: > >> If you don't need to use Fortran, you can configure with --disable-fortran. >> >> Rajeev >> >> On Apr 8, 2015, at 10:36 PM, Lou Picciano <loupicciano(a)comcast.net> wrote: >> >>> Attempting to configure mpich-3.2b1 for the SolarisStudio12.4 suite... >>> >>> Issues around complex.h (Yes, I'll have to look for prerequisites) >>> >>> and the message about FORTRAN integer length - which seems to have been dealt with a couple of years ago, and only in the ifort context? >>> >>> CROSS_F77_SIZEOF_INTEGER seems to be ignored; I've tried all of 1,2,4,8... >>> >>> Many thanks! >>> >>> checking complex.h presence... yes >>> configure: WARNING: complex.h: present but cannot be compiled >>> configure: WARNING: complex.h: check for missing prerequisite headers? >>> configure: WARNING: complex.h: see the Autoconf documentation >>> configure: WARNING: complex.h: section "Present But Cannot Be Compiled" >>> configure: WARNING: complex.h: proceeding with the compiler's result >>> configure: WARNING: ## -------------------------------- ## >>> configure: WARNING: ## Report this to discuss(a)mpich.org ## >>> configure: WARNING: ## -------------------------------- ## >>> checking for complex.h... no >>> checking size of _Bool... 0 >>> checking size of float _Complex... 0 >>> checking size of double _Complex... 0 >>> checking size of long double _Complex... 0 >>> checking for _Bool... no >>> checking for float _Complex... no >>> checking for double _Complex... no >>> checking for long double _Complex... no >>> checking for size of Fortran type integer... 0 >>> checking for size of Fortran type real... 0 >>> checking for size of Fortran type double precision... 0 >>> checking whether integer*1 is supported... yes >>> checking whether integer*2 is supported... yes >>> checking whether integer*4 is supported... yes >>> checking whether integer*8 is supported... yes >>> checking whether integer*16 is supported... no >>> checking whether real*4 is supported... yes >>> checking whether real*8 is supported... yes >>> checking whether real*16 is supported... yes >>> configure: error: Unable to configure with Fortran support because configure could not determine the size of a Fortran INTEGER. Consider setting CROSS_F77_SIZEOF_INTEGER to the length in bytes of a Fortran INTEGER >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] return() or exit() from int main() (NOT MPICH SPECIFIC)
by Michael L. Stokes 10 Apr '15

10 Apr '15

Michael, Good question. Since this is the MPICH forum, I ran some test cases on a CRAY, and a 64bit PC: For the CRAY using the cray-mpich/6.3.1 module. The code simply initializes MPI and returns its rank. The code (exit_test.C) follows: #include <iostream> #include <cstdlib> #include <mpi.h> int main(void) { int rank; MPI_Init(0,0); MPI_Comm_rank( MPI_COMM_WORLD, &rank); if( rank == 0 ) { int size; MPI_Comm_size( MPI_COMM_WORLD, &size); std::cout << "Rank:" << rank << ", size:" << size << std::endl; } MPI_Finalize(); return rank; } I compiled with CC exit_test.C -o exit_test and executed with the following (PBS_INTERACTIVE) aprun -n 7 ./exit_test I was surprised with the result. I ran it probably a dozen times. Here are a few runs ... xxx@batch2:~/src/MPI/tmp> aprun -n 7 ./exit_test Rank:0, size:7 Application 13573540 exit codes: 6 Application 13573540 resources: utime ~0s, stime ~1s, Rss ~39164, inblocks ~10234, outblocks ~23470 xxx@batch2:~/src/MPI/tmp> echo $? 6 xxx@batch2:~/src/MPI/tmp> aprun -n 7 ./exit_test Rank:0, size:7 Application 13573552 exit codes: 4 Application 13573552 resources: utime ~0s, stime ~1s, Rss ~39164, inblocks ~10234, outblocks ~23470 xxx@batch2:~/src/MPI/tmp> echo $? 4 xxx@batch2:~/src/MPI/tmp> aprun -n 7 ./exit_test Rank:0, size:7 Application 13573564 exit codes: 1 Application 13573564 resources: utime ~0s, stime ~1s, Rss ~39172, inblocks ~10234, outblocks ~23470 xxx@batch2:~/src/MPI/tmp> echo $? 1 xxx@batch2:~/src/MPI/tmp> aprun -n 7 ./exit_test Rank:0, size:7 Application 13573589 exit codes: 5 Application 13573589 resources: utime ~0s, stime ~1s, Rss ~39188, inblocks ~10234, outblocks ~23470 xxx@batch2:~/src/MPI/tmp> echo $? 5 I say surprised because the man page taken from http://www.mpich.org/static/docs/v3.1/www1/mpiexec.html reports the following ... Return Status mpiexec returns the maximum of the exit status values of all of the processes created by mpiexec. But the fine Cray folk have probably mucked with the MPI executive, so the results running on the XC30 might not agree with the MPICH man page. I also ran this test on a PC running UBUNTU 12.04, with source built MPICH 3.1.2. Here are a few of those results Compile line: mpicc exit_test.C -o exit_test Here are results from this test. Note than I am varying the processor count here. xxx@Cue ~/tmp/MPI $ mpiexec -np 9 ./exit_test Rank:0, size:9 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 19062 RUNNING AT Cue = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== xxx@Cue ~/tmp/MPI $ echo $? 15 xxx@Cue ~/tmp/MPI $ mpiexec -np 8 ./exit_test Rank:0, size:8 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 19130 RUNNING AT Cue = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== xxx@Cue ~/tmp/MPI $ echo $? 7 xxx@Cue ~/tmp/MPI $ mpiexec -np 7 ./exit_test Rank:0, size:7 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 19142 RUNNING AT Cue = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== xxx@Cue ~/tmp/MPI $ echo $? 7 xxx@Cue ~/tmp/MPI $ mpiexec -np 3 ./exit_test Rank:0, size:3 =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 19158 RUNNING AT Cue = EXIT CODE: 1 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES =================================================================================== xxx@Cue ~/tmp/MPI $ echo $? 3 So unlike the test on the CRAY, the results on the PC are consistent, but do not agree with the man page. Michael to address your question, it is certainly implementation dependent. There are any number of ways to report the exit status. MPICH docs suggest taking the maximum value. Another approach is to use the exit status of the root process. As a side note, MPICH acknowledges that a non-zero return value results in a bad termination. If I run the later case with np=1, I get xxx@Cue ~/tmp/MPI $ mpiexec -np 1 ./exit_test Rank:0, size:1 xxx@Cue ~/tmp/MPI $ echo $? 0 which is what I would expect. --Mike On 04/09/2015 02:27 PM, Michael Raymond wrote: > Hi. I'm the lead developer of SGI MPI. > > Do other MPIs do something different here? As you might have > thousands of ranks, I'm wondering how you'd decide which exit code to > return? > > On 04/09/2015 11:36 AM, Michael L. Stokes wrote: >> This question is not MPICH specific, but I'm sure the expertise is here >> to answer this question. >> >> While running tests on spirit.afrl.hpc.mil (SGI ICE X) using the >> MPT/2.11 stack, I noticed that mpirun returns 0 to the shell regardless >> of the exit value ( <stdlib.h> exit(int) ), or the return value >> (return(int)) from the main. >> >> Would this behavior be regarded as an error? What are the issues? >> >> --Mike >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0