Re: [OMPI users] latest stable and win7/msvc2013

[Michael.Rachner]

Dear people,

As a continuation of the hint of   Damien   , who suggested using MPICH on WIN7 
:

MPICH has already stopped supporting WINDOWS in the past. MPICH recommends 
using  MS-MPI for WINDOWS, which is a derivative from MPICH2.
You may download the binary (for free) from the landing page for MS-MPI:  
http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx
Most recent version is:version: 4.2.4400.0   Date published: 1/14/2014
However note, that MS-MPI does conform to MPI-2, not yet to MPI-3.
The installation is easy and it works well with my CFD-code under WIN7 (64-bit).

Greetings
Michael Rachner



Von: users [mailto:users-boun...@open-mpi.org] Im Auftrag von Damien
Gesendet: Mittwoch, 16. Juli 2014 18:15
An: us...@open-mpi.org
Betreff: Re: [OMPI users] latest stable and win7/msvc2013

Guys,

Don't do it.  It doesn't work at all.  I couldn't pick up maintenance of it 
either, and the majority of the Windows support is removed as Ralph said.  Just 
use MPICH for Windows work and save yourself the pain.

Cheers,

Damien
On 2014-07-16 9:57 AM, Nathan Hjelm wrote:

It likely won't build because last I check the Microsoft toolchain does

not fit the minimum requirements (C99 or higher). You will have better

luck with either gcc or intel's compiler.



-Nathan



On Wed, Jul 16, 2014 at 04:52:53PM +0100, MM wrote:

hello,

I'm about to try to build 1.8.1 with win msvc2013 toolkit in 64bit mode.

I know the win binaries were dropped after failure to find someone to

pick them up (following shiqin departure), and i'm afraid I wouldn't

volunteer due to lack of time, but is there any general advice before

I start?



rds,

MM

___

users mailing list

us...@open-mpi.org

Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users

Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24787.php




___

users mailing list

us...@open-mpi.org

Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users

Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24789.php

Re: [OMPI users] latest stable and win7/msvc2013

[Ralph Castain]

FWIW: now that I have access to the Intel compiler suite, including for 
Windows, I've been toying with creating a more stable support solution for OMPI 
on Windows. It's a low-priority task for me because it isn't clear that we have 
very many Windows users in HPC land, and the cygwin port already exists anyway. 
However, I probably will do it for sometime in the 1.9 series.


On Jul 17, 2014, at 1:14 AM, michael.rach...@dlr.de wrote:

> Dear people,
>  
> As a continuation of the hint of   Damien   , who suggested using MPICH on 
> WIN7 :
>  
> MPICH has already stopped supporting WINDOWS in the past. MPICH recommends 
> using  MS-MPI for WINDOWS, which is a derivative from MPICH2.
> You may download the binary (for free) from the landing page for MS-MPI:  
> http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx
> Most recent version is:version: 4.2.4400.0   Date published: 1/14/2014
> However note, that MS-MPI does conform to MPI-2, not yet to MPI-3.
> The installation is easy and it works well with my CFD-code under WIN7 
> (64-bit).
>  
> Greetings
> Michael Rachner
>  
>  
>  
> Von: users [mailto:users-boun...@open-mpi.org] Im Auftrag von Damien
> Gesendet: Mittwoch, 16. Juli 2014 18:15
> An: us...@open-mpi.org
> Betreff: Re: [OMPI users] latest stable and win7/msvc2013
>  
> Guys,
> 
> Don't do it.  It doesn't work at all.  I couldn't pick up maintenance of it 
> either, and the majority of the Windows support is removed as Ralph said.  
> Just use MPICH for Windows work and save yourself the pain.
> 
> Cheers,
> 
> Damien
> 
> On 2014-07-16 9:57 AM, Nathan Hjelm wrote:
> It likely won't build because last I check the Microsoft toolchain does
> not fit the minimum requirements (C99 or higher). You will have better
> luck with either gcc or intel's compiler.
>  
> -Nathan
>  
> On Wed, Jul 16, 2014 at 04:52:53PM +0100, MM wrote:
> hello,
> I'm about to try to build 1.8.1 with win msvc2013 toolkit in 64bit mode.
> I know the win binaries were dropped after failure to find someone to
> pick them up (following shiqin departure), and i'm afraid I wouldn't
> volunteer due to lack of time, but is there any general advice before
> I start?
>  
> rds,
> MM
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/07/24787.php
> 
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/07/24789.php
>  
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/07/24793.php

Re: [OMPI users] Salloc and mpirun problem

[Timur Ismagilov]

With Open MPI 1.9a1r32252 (Jul 16, 2014 (nightly snapshot tarball)) i got this 
output (same?):
$ salloc -N2 --exclusive -p test -J ompi
salloc: Granted job allocation 645686

$LD_PRELOAD=/mnt/data/users/dm2/vol3/semenov/_scratch/mxm/mxm-3.0/lib/libmxm.so 
 mpirun  -mca mca_base_env_list 'LD_PRELOAD'  --mca plm_base_verbose 10 
--debug-daemons -np 1 hello_c
[access1:04312] mca: base: components_register: registering plm components
[access1:04312] mca: base: components_register: found loaded component isolated
[access1:04312] mca: base: components_register: component isolated has no 
register or open function
[access1:04312] mca: base: components_register: found loaded component rsh
[access1:04312] mca: base: components_register: component rsh register function 
successful
[access1:04312] mca: base: components_register: found loaded component slurm
[access1:04312] mca: base: components_register: component slurm register 
function successful
[access1:04312] mca: base: components_open: opening plm components
[access1:04312] mca: base: components_open: found loaded component isolated
[access1:04312] mca: base: components_open: component isolated open function 
successful
[access1:04312] mca: base: components_open: found loaded component rsh
[access1:04312] mca: base: components_open: component rsh open function 
successful
[access1:04312] mca: base: components_open: found loaded component slurm
[access1:04312] mca: base: components_open: component slurm open function 
successful
[access1:04312] mca:base:select: Auto-selecting plm components
[access1:04312] mca:base:select:( plm) Querying component [isolated]
[access1:04312] mca:base:select:( plm) Query of component [isolated] set 
priority to 0
[access1:04312] mca:base:select:( plm) Querying component [rsh]
[access1:04312] mca:base:select:( plm) Query of component [rsh] set priority to 
10
[access1:04312] mca:base:select:( plm) Querying component [slurm]
[access1:04312] mca:base:select:( plm) Query of component [slurm] set priority 
to 75
[access1:04312] mca:base:select:( plm) Selected component [slurm]
[access1:04312] mca: base: close: component isolated closed
[access1:04312] mca: base: close: unloading component isolated
[access1:04312] mca: base: close: component rsh closed
[access1:04312] mca: base: close: unloading component rsh
Daemon was launched on node1-128-09 - beginning to initialize
Daemon was launched on node1-128-15 - beginning to initialize
Daemon [[39207,0],1] checking in as pid 26240 on host node1-128-09
[node1-128-09:26240] [[39207,0],1] orted: up and running - waiting for commands!
Daemon [[39207,0],2] checking in as pid 30129 on host node1-128-15
[node1-128-15:30129] [[39207,0],2] orted: up and running - waiting for commands!
srun: error: node1-128-09: task 0: Exited with exit code 1
srun: Terminating job step 645686.3
srun: error: node1-128-15: task 1: Exited with exit code 1
--
An ORTE daemon has unexpectedly failed after launch and before
communicating back to mpirun. This could be caused by a number
of factors, including an inability to create a connection back
to mpirun due to a lack of common network interfaces and/or no
route found between them. Please check network connectivity
(including firewalls and network routing requirements).
--
[access1:04312] [[39207,0],0] orted_cmd: received halt_vm cmd
[access1:04312] mca: base: close: component slurm closed
[access1:04312] mca: base: close: unloading component slurm


Thu, 17 Jul 2014 11:40:24 +0300 от Mike Dubman :
>can you use latest ompi-1.8 from svn/git?
>Ralph - could you please suggest.
>Thx
>
>
>On Wed, Jul 16, 2014 at 2:48 PM, Timur Ismagilov  < tismagi...@mail.ru > wrote:
>>Here it is:
>>
>>$ 
>>LD_PRELOAD=/mnt/data/users/dm2/vol3/semenov/_scratch/mxm/mxm-3.0/lib/libmxm.so
>>  mpirun  -x LD_PRELOAD --mca plm_base_verbose 10 --debug-daemons -np 1 
>>hello_c
>>
>>[access1:29064] mca: base: components_register: registering plm components
>>[access1:29064] mca: base: components_register: found loaded component 
>>isolated
>>[access1:29064] mca: base: components_register: component isolated has no 
>>register or open function
>>[access1:29064] mca: base: components_register: found loaded component rsh
>>[access1:29064] mca: base: components_register: component rsh register 
>>function successful
>>[access1:29064] mca: base: components_register: found loaded component slurm
>>[access1:29064] mca: base: components_register: component slurm register 
>>function successful
>>[access1:29064] mca: base: components_open: opening plm components
>>[access1:29064] mca: base: components_open: found loaded component isolated
>>[access1:29064] mca: base: components_open: component isolated open function 
>>successful
>>[access1:29064] mca: base: components_open: found loaded component rsh
>>[access1:29064] mca: base: components_open: component rsh open 

Re: [OMPI users] latest stable and win7/msvc2013

[Rob Latham]

On 07/17/2014 05:48 AM, Ralph Castain wrote:

FWIW: now that I have access to the Intel compiler suite, including for
Windows, I've been toying with creating a more stable support solution
for OMPI on Windows. It's a low-priority task for me because it isn't
clear that we have very many Windows users in HPC land, and the cygwin
port already exists anyway. However, I probably will do it for sometime
in the 1.9 series.


Well, I (and dgoodell and jsquyers and probably a few others of you) can 
say from observing disc...@mpich.org traffic that we get one message 
about Windows support every month -- probably more often.  There's 
clearly a community of Windows users out there looking for a free MPI 
implementation.


Sorry to hear that MS-MPI is not yet MPI-3 compliant. There is also 
Intel-MPI and Platform-MPI but I think you have to license those?


==rob




On Jul 17, 2014, at 1:14 AM, michael.rach...@dlr.de
 wrote:


Dear people,
As a continuation of the hint of   Damien   , who suggested using
MPICH on WIN7 :
MPICH has already stopped supporting WINDOWS in the past. MPICH
recommends using  MS-MPI for WINDOWS, which is a derivative from MPICH2.
You may download the binary (for free) from the landing page for
MS-MPI: http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx
Most recent version is:version: 4.2.4400.0   Date published:
1/14/2014
However note, that MS-MPI does conform to MPI-2, not yet to MPI-3.
The installation is easy and it works well with my CFD-code under WIN7
(64-bit).
Greetings
Michael Rachner
*Von:*users [mailto:users-boun...@open-mpi.org]*Im Auftrag von*Damien
*Gesendet:*Mittwoch, 16. Juli 2014 18:15
*An:*us...@open-mpi.org 
*Betreff:*Re: [OMPI users] latest stable and win7/msvc2013

Guys,

Don't do it.  It doesn't work at all.  I couldn't pick up maintenance
of it either, and the majority of the Windows support is removed as
Ralph said.  Just use MPICH for Windows work and save yourself the pain.

Cheers,

Damien

On 2014-07-16 9:57 AM, Nathan Hjelm wrote:

It likely won't build because last I check the Microsoft toolchain does

not fit the minimum requirements (C99 or higher). You will have better

luck with either gcc or intel's compiler.



-Nathan



On Wed, Jul 16, 2014 at 04:52:53PM +0100, MM wrote:

hello,

I'm about to try to build 1.8.1 with win msvc2013 toolkit in 64bit mode.

I know the win binaries were dropped after failure to find someone to

pick them up (following shiqin departure), and i'm afraid I wouldn't

volunteer due to lack of time, but is there any general advice before

I start?



rds,

MM

___

users mailing list

us...@open-mpi.org  

Subscription:http://www.open-mpi.org/mailman/listinfo.cgi/users

Link to this 
post:http://www.open-mpi.org/community/lists/users/2014/07/24787.php




___

users mailing list

us...@open-mpi.org  

Subscription:http://www.open-mpi.org/mailman/listinfo.cgi/users

Link to this 
post:http://www.open-mpi.org/community/lists/users/2014/07/24789.php

___
users mailing list
us...@open-mpi.org 
Subscription:http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this
post:http://www.open-mpi.org/community/lists/users/2014/07/24793.php




___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24794.php



--
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA

Re: [OMPI users] latest stable and win7/msvc2013

[Jed Brown]

Rob Latham  writes:
> Well, I (and dgoodell and jsquyers and probably a few others of you) can 
> say from observing disc...@mpich.org traffic that we get one message 
> about Windows support every month -- probably more often.

Seems to average at least once a week.  We also see regular petsc
support emails wondering why --download-{mpich,openmpi} does not work on
Windows.  (These options are pretty much only used by beginners for whom
PETSc is their first encounter with MPI.)


pgpTrcUQKFdOM.pgp
Description: PGP signature

Re: [OMPI users] latest stable and win7/msvc2013

[Ralph Castain]

Guess we just haven't seen that much activity on the OMPI list, even when we 
did support Windows. I'll see what I can do - I think this new method will 
allow it to be stable and require far less maintenance than what we had before.


On Jul 17, 2014, at 10:42 AM, Jed Brown  wrote:

> Rob Latham  writes:
>> Well, I (and dgoodell and jsquyers and probably a few others of you) can 
>> say from observing disc...@mpich.org traffic that we get one message 
>> about Windows support every month -- probably more often.
> 
> Seems to average at least once a week.  We also see regular petsc
> support emails wondering why --download-{mpich,openmpi} does not work on
> Windows.  (These options are pretty much only used by beginners for whom
> PETSc is their first encounter with MPI.)
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/07/24797.php

Re: [OMPI users] latest stable and win7/msvc2013

[Damien]

Is this something that could be funded by Microsoft, and is it time to 
approach them perhaps?  MS MPI is based on MPICH, and if mainline MPICH 
isn't supporting Windows anymore, then there won't be a whole lot of 
development in an increasingly older Windows build.  With the Open-MPI 
roadmap, there's a lot happening.  Would it be a better business model 
for MS to piggy-back off of Open-MPI ongoing innovation, and put their 
resources into maintaining a Windows build of Open-MPI instead?


Damien

On 2014-07-17 11:42 AM, Jed Brown wrote:

Rob Latham  writes:

Well, I (and dgoodell and jsquyers and probably a few others of you) can
say from observing disc...@mpich.org traffic that we get one message
about Windows support every month -- probably more often.

Seems to average at least once a week.  We also see regular petsc
support emails wondering why --download-{mpich,openmpi} does not work on
Windows.  (These options are pretty much only used by beginners for whom
PETSc is their first encounter with MPI.)


___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24797.php

Re: [OMPI users] latest stable and win7/msvc2013

[Jed Brown]

Damien  writes:

> Is this something that could be funded by Microsoft, and is it time to 
> approach them perhaps?  MS MPI is based on MPICH, and if mainline MPICH 
> isn't supporting Windows anymore, then there won't be a whole lot of 
> development in an increasingly older Windows build.  With the Open-MPI 
> roadmap, there's a lot happening.  Would it be a better business model 
> for MS to piggy-back off of Open-MPI ongoing innovation, and put their 
> resources into maintaining a Windows build of Open-MPI instead?

Maybe Fab can comment on Microsoft's intentions regarding MPI and
C99/C11 (just dreaming now).

> On 2014-07-17 11:42 AM, Jed Brown wrote:
>> Rob Latham  writes:
>>> Well, I (and dgoodell and jsquyers and probably a few others of you) can
>>> say from observing disc...@mpich.org traffic that we get one message
>>> about Windows support every month -- probably more often.
>> Seems to average at least once a week.  We also see regular petsc
>> support emails wondering why --download-{mpich,openmpi} does not work on
>> Windows.  (These options are pretty much only used by beginners for whom
>> PETSc is their first encounter with MPI.)


pgpNqLEhkDbvI.pgp
Description: PGP signature

Re: [OMPI users] latest stable and win7/msvc2013

[Rob Latham]

On 07/17/2014 01:19 PM, Jed Brown wrote:

Damien  writes:


Is this something that could be funded by Microsoft, and is it time to
approach them perhaps?  MS MPI is based on MPICH, and if mainline MPICH
isn't supporting Windows anymore, then there won't be a whole lot of
development in an increasingly older Windows build.  With the Open-MPI
roadmap, there's a lot happening.  Would it be a better business model
for MS to piggy-back off of Open-MPI ongoing innovation, and put their
resources into maintaining a Windows build of Open-MPI instead?


Maybe Fab can comment on Microsoft's intentions regarding MPI and
C99/C11 (just dreaming now).


hey, (almost all of) c99 support is in place in visual studio 2013
http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx

==rob




On 2014-07-17 11:42 AM, Jed Brown wrote:

Rob Latham  writes:

Well, I (and dgoodell and jsquyers and probably a few others of you) can
say from observing disc...@mpich.org traffic that we get one message
about Windows support every month -- probably more often.

Seems to average at least once a week.  We also see regular petsc
support emails wondering why --download-{mpich,openmpi} does not work on
Windows.  (These options are pretty much only used by beginners for whom
PETSc is their first encounter with MPI.)


___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24800.php


--
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA

Re: [OMPI users] latest stable and win7/msvc2013

[Ralph Castain]

Yeah, but I'm cheap and get the Intel compilers for free :-)


On Jul 17, 2014, at 11:38 AM, Rob Latham  wrote:

> 
> 
> On 07/17/2014 01:19 PM, Jed Brown wrote:
>> Damien  writes:
>> 
>>> Is this something that could be funded by Microsoft, and is it time to
>>> approach them perhaps?  MS MPI is based on MPICH, and if mainline MPICH
>>> isn't supporting Windows anymore, then there won't be a whole lot of
>>> development in an increasingly older Windows build.  With the Open-MPI
>>> roadmap, there's a lot happening.  Would it be a better business model
>>> for MS to piggy-back off of Open-MPI ongoing innovation, and put their
>>> resources into maintaining a Windows build of Open-MPI instead?
>> 
>> Maybe Fab can comment on Microsoft's intentions regarding MPI and
>> C99/C11 (just dreaming now).
> 
> hey, (almost all of) c99 support is in place in visual studio 2013
> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx
> 
> ==rob
> 
>> 
>>> On 2014-07-17 11:42 AM, Jed Brown wrote:
 Rob Latham  writes:
> Well, I (and dgoodell and jsquyers and probably a few others of you) can
> say from observing disc...@mpich.org traffic that we get one message
> about Windows support every month -- probably more often.
 Seems to average at least once a week.  We also see regular petsc
 support emails wondering why --download-{mpich,openmpi} does not work on
 Windows.  (These options are pretty much only used by beginners for whom
 PETSc is their first encounter with MPI.)
 
 
 ___
 users mailing list
 us...@open-mpi.org
 Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
 Link to this post: 
 http://www.open-mpi.org/community/lists/users/2014/07/24800.php
> 
> -- 
> Rob Latham
> Mathematics and Computer Science Division
> Argonne National Lab, IL USA
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2014/07/24801.php

Re: [OMPI users] latest stable and win7/msvc2013

[Jed Brown]

Rob Latham  writes:
> hey, (almost all of) c99 support is in place in visual studio 2013
> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx

This talks about the standard library, but not whether the C frontend
has acquired these features.  Are they attempting to support C99 or
merely providing some features to C++ users?

BTW, did Microsoft ever fix the misimplementation of variadic macros?

http://stackoverflow.com/questions/5134523/msvc-doesnt-expand-va-args-correctly


pgp47P3r85ypC.pgp
Description: PGP signature

Re: [OMPI users] latest stable and win7/msvc2013

[Jed Brown]

Ralph Castain  writes:

> Yeah, but I'm cheap and get the Intel compilers for free :-)

Fine for you, but not for the people trying to integrate your library
in a stack developed using MSVC.


pgpDnaWHH5nyy.pgp
Description: PGP signature

Re: [OMPI users] latest stable and win7/msvc2013

[Ralph Castain]

Well, yeah - I dig that. However, barring doing something stupid, I am hopeful 
we'll be okay if I continue OMPI's practice of staying within the C99 standard. 
If MSVC won't support that, then we're out of luck anyway because there is no 
way OMPI is going back to pre-C99 at this stage.


On Jul 17, 2014, at 11:52 AM, Jed Brown  wrote:

> Ralph Castain  writes:
> 
>> Yeah, but I'm cheap and get the Intel compilers for free :-)
> 
> Fine for you, but not for the people trying to integrate your library
> in a stack developed using MSVC.

Re: [OMPI users] latest stable and win7/msvc2013

[Damien]

Visual Studio can link libs compiled with Intel.  We used to make 
binaries available for Windows with Open-MPI.


On 2014-07-17 12:58 PM, Ralph Castain wrote:

Well, yeah - I dig that. However, barring doing something stupid, I am hopeful 
we'll be okay if I continue OMPI's practice of staying within the C99 standard. 
If MSVC won't support that, then we're out of luck anyway because there is no 
way OMPI is going back to pre-C99 at this stage.


On Jul 17, 2014, at 11:52 AM, Jed Brown  wrote:

Re: [OMPI users] latest stable and win7/msvc2013

[Jed Brown]

Damien  writes:

> Visual Studio can link libs compiled with Intel.  

The headers also need to fall within the language subset implemented by
MSVC, but this is easier to ensure and the Windows ecosystem seems to be
happy with binary distribution.


pgpHHN3ASH0QJ.pgp
Description: PGP signature

Re: [OMPI users] latest stable and win7/msvc2013

[n8tm]

If you support with intel fortran why not intel c99? User can still use msvc

Tim Prince

 Original message 
From: Ralph Castain  
Date:  
To: Jed Brown  
Cc: Open MPI Users  
Subject: Re: [OMPI users] latest stable and win7/msvc2013 
 
Well, yeah - I dig that. However, barring doing something stupid, I am hopeful 
we'll be okay if I continue OMPI's practice of staying within the C99 standard. 
If MSVC won't support that, then we're out of luck anyway because there is no 
way OMPI is going back to pre-C99 at this stage.


On Jul 17, 2014, at 11:52 AM, Jed Brown  wrote:

> Ralph Castain  writes:
> 
>> Yeah, but I'm cheap and get the Intel compilers for free :-)
> 
> Fine for you, but not for the people trying to integrate your library
> in a stack developed using MSVC.

___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2014/07/24805.php

Re: [OMPI users] latest stable and win7/msvc2013

[Fab Tillier]

[resending now that I've joined the Open MPI users list, sorry for the 
duplicate]

Hi Jed,

Thanks for looping me on this mail thread. 

Jed Brown wrote on Thu, 17 Jul 2014 at 11:19:42

> Damien  writes:
> 
>> Is this something that could be funded by Microsoft, and is it time 
>> to approach them perhaps?  MS MPI is based on MPICH, and if mainline 
>> MPICH isn't supporting Windows anymore, then there won't be a whole 
>> lot of development in an increasingly older Windows build. With the
>> Open-MPI roadmap, there's a lot happening.

Open-MPI isn't supporting Windows anymore either, and I would think it fair to 
say that a lot is happening in both Open-MPI and MPICH (for non-Windows 
environments).

>> Would it be a
>> better business model for MS to piggy-back off of Open-MPI ongoing 
>> innovation, and put their resources into maintaining a Windows build 
>> of Open-MPI instead?

Microsoft doesn't simply maintain a Windows build of MPICH.  While MS-MPI is 
derived from MPICH, at this point it is really a more of a fork given how much 
Windows-specific work we've done that isn't applicable to the mainline MPICH 
development.  We're continuing to invest in the development of MS-MPI, and our 
focus continues to be on user-requested features.  We strongly believe that 
users care more about feature content than which codebase we are derived from - 
after all, portability is one of the main goals of the MPI standard.

We've worked very hard to maintain ABI over the various versions of MS-MPI, and 
a fundamental shift to a different implementation would wreak havoc on users 
and our ISV partners.

> Maybe Fab can comment on Microsoft's intentions regarding MPI and
> C99/C11 (just dreaming now).

I can't really comment on the C99/C11 stuff, as that's a completely different 
organization within Microsoft.  Rob seems to have shed some light on this 
(thanks for finding that Rob!)

>From an MPI perspective, we've been investing in making ourselves available to 
>our user and developer community, whether through email 
>(mailto:ask...@microsoft.com, CC'd), through our beta program on Microsoft 
>Connect (https://connect.microsoft.com/HPC/MS-MPI), where users can request 
>(and vote for) features (https://connect.microsoft.com/HPC/Feedback), or 
>through our web forums 
>(http://social.microsoft.com/Forums/en-US/home?forum=windowshpcmpi).  We'd 
>very much like to get input from our user community to help shape our features 
>content going forward.

I'm not familiar with PETSc, but would be happy to develop a closer 
relationship with the developers to enable better integration of MS-MPI into 
the PETSc environment.  Conceptually, a --download-msmpi option would be great, 
and we already allow redistribution of our installer package with third party 
applications (to enable bundling) if that makes more sense.

-Fab

>> On 2014-07-17 11:42 AM, Jed Brown wrote:
>>> Rob Latham  writes:
 Well, I (and dgoodell and jsquyers and probably a few others of
 you) can say from observing disc...@mpich.org traffic that we get 
 one message about Windows support every month -- probably more often.
>>> Seems to average at least once a week.  We also see regular petsc 
>>> support emails wondering why --download-{mpich,openmpi} does not 
>>> work on Windows.  (These options are pretty much only used by 
>>> beginners for whom PETSc is their first encounter with MPI.)

Re: [OMPI users] latest stable and win7/msvc2013

[Damien]

Fair enough, all good business reasons not to switch MPI platforms at 
Microsoft's end.


Damien

On 2014-07-17 4:29 PM, Fab Tillier wrote:

[resending now that I've joined the Open MPI users list, sorry for the 
duplicate]

Hi Jed,

Thanks for looping me on this mail thread.

Jed Brown wrote on Thu, 17 Jul 2014 at 11:19:42


Damien  writes:


Is this something that could be funded by Microsoft, and is it time
to approach them perhaps?  MS MPI is based on MPICH, and if mainline
MPICH isn't supporting Windows anymore, then there won't be a whole
lot of development in an increasingly older Windows build. With the
Open-MPI roadmap, there's a lot happening.

Open-MPI isn't supporting Windows anymore either, and I would think it fair to 
say that a lot is happening in both Open-MPI and MPICH (for non-Windows 
environments).


Would it be a
better business model for MS to piggy-back off of Open-MPI ongoing
innovation, and put their resources into maintaining a Windows build
of Open-MPI instead?

Microsoft doesn't simply maintain a Windows build of MPICH.  While MS-MPI is 
derived from MPICH, at this point it is really a more of a fork given how much 
Windows-specific work we've done that isn't applicable to the mainline MPICH 
development.  We're continuing to invest in the development of MS-MPI, and our 
focus continues to be on user-requested features.  We strongly believe that 
users care more about feature content than which codebase we are derived from - 
after all, portability is one of the main goals of the MPI standard.

We've worked very hard to maintain ABI over the various versions of MS-MPI, and 
a fundamental shift to a different implementation would wreak havoc on users 
and our ISV partners.


Maybe Fab can comment on Microsoft's intentions regarding MPI and
C99/C11 (just dreaming now).

I can't really comment on the C99/C11 stuff, as that's a completely different 
organization within Microsoft.  Rob seems to have shed some light on this 
(thanks for finding that Rob!)

 From an MPI perspective, we've been investing in making ourselves available to 
our user and developer community, whether through email 
(mailto:ask...@microsoft.com, CC'd), through our beta program on Microsoft 
Connect (https://connect.microsoft.com/HPC/MS-MPI), where users can request 
(and vote for) features (https://connect.microsoft.com/HPC/Feedback), or 
through our web forums 
(http://social.microsoft.com/Forums/en-US/home?forum=windowshpcmpi).  We'd very 
much like to get input from our user community to help shape our features 
content going forward.

I'm not familiar with PETSc, but would be happy to develop a closer 
relationship with the developers to enable better integration of MS-MPI into 
the PETSc environment.  Conceptually, a --download-msmpi option would be great, 
and we already allow redistribution of our installer package with third party 
applications (to enable bundling) if that makes more sense.

-Fab


On 2014-07-17 11:42 AM, Jed Brown wrote:

Rob Latham  writes:

Well, I (and dgoodell and jsquyers and probably a few others of
you) can say from observing disc...@mpich.org traffic that we get
one message about Windows support every month -- probably more often.

Seems to average at least once a week.  We also see regular petsc
support emails wondering why --download-{mpich,openmpi} does not
work on Windows.  (These options are pretty much only used by
beginners for whom PETSc is their first encounter with MPI.)