Please review the NEWS bullets for 1.7.4 on the trunk, and add any missing
items, make corrections, etc.
Ralph: in particular, I'm sure I missed some ORTE-related bullets.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/le
Just as an inducement: I believe 1.7.4 is complete at this time. The MTT runs
look exceptionally clean, and we thoroughly beat this version up in the time
since rc1.
So this is going to be a quick "smoke test" period prior to final release.
Please give it a once-over to confirm nothing was inad
In the usual location:
http://www.open-mpi.org/software/ompi/v1.7/
Lots of changes since 1.7.4rc1, but we didn't keep a good NEWS file between the
two, so I can't list them all here.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/d
On Jan 27, 2014, at 1:24 PM, Nathan Hjelm wrote:
> On Mon, Jan 27, 2014 at 01:10:43PM -0800, Ralph Castain wrote:
>> Nathan, I have no idea what you are talking about. What I do know is that
>> you had me commit a patch to the trunk and v1.7.4 that caused multiple
>> warnings about 32-bit issu
On Mon, Jan 27, 2014 at 01:10:43PM -0800, Ralph Castain wrote:
> Nathan, I have no idea what you are talking about. What I do know is that you
> had me commit a patch to the trunk and v1.7.4 that caused multiple warnings
> about 32-bit issues to appear in both cases. George is reporting issues th
Nathan, I have no idea what you are talking about. What I do know is that you
had me commit a patch to the trunk and v1.7.4 that caused multiple warnings
about 32-bit issues to appear in both cases. George is reporting issues that
look very much like the ones I'd expect based on those warnings.
Nope. Vader will not work on non-xpmem systems in 1.7.4. The CMR is
still open for 1.7.5 (#4053. Issue like the one George reported are
why I chose to hold off on the new vader until 1.7.5.
The fix is complete. At this point I am waiting on some feedback on
changes to OMPI_CHECK_PACKAGE before com
Nathan,
To encourage you to focus on 1.7.4, I will delay testing vader on the SGI
UV until I've tested the next 1.7.4 release candidate (or final).
-Paul
On Mon, Jan 27, 2014 at 12:55 PM, Ralph Castain wrote:
> Just FWIW: I believe that problem did indeed make it over to 1.7.4, and
> that rel
Just FWIW: I believe that problem did indeed make it over to 1.7.4, and that
release is on "hold" pending your fix. So while I'm happy to hear about xpmem
on SGI, please do let us release 1.7.4!
On Jan 27, 2014, at 8:19 AM, Nathan Hjelm wrote:
> Yup. Has to do with not having 64-bit atomic ma
Thanks Jeff,
we will check and address it.
On Fri, Jan 24, 2014 at 7:13 PM, Jeff Squyres (jsquyres) wrote:
> Mellanox --
>
> Some comments on the commit below.
>
>
> On Jan 23, 2014, at 2:49 AM, svn-commit-mai...@open-mpi.org wrote:
>
> > Modified: trunk/config/oshmem_configure_options.m4
> >
>
Yup. Has to do with not having 64-bit atomic math. The fix is complete
but I am working on another update to enable using xpmem on SGI
systems. I will push the changes once that is complete.
-Nathan
On Mon, Jan 27, 2014 at 04:00:08PM +, Jeff Squyres (jsquyres) wrote:
> Is this the same issue
I have the following patches which I would like to commit. All changes
are in the SNAPC component. The first patch replaces all statically
allocated buffers with dynamically allocate buffers. The second patch
removes compiler warnings and the last patch tries to re-introduce
functionality which I r
Is this the same issue Absoft is seeing in 32 bit builds on the trunk? (i.e.,
100% failure rate)
http://mtt.open-mpi.org/index.php?do_redir=2142
On Jan 27, 2014, at 10:38 AM, Nathan Hjelm wrote:
> This shouldn't be affecting 1.7.4 since neither the vader or coll/ml
> updates have been mo
This shouldn't be affecting 1.7.4 since neither the vader or coll/ml
updates have been moved yet. As for trunk I am working on a 32-bit fix
for vader and it should be in later today. I will have to track down
what is going wrong the basesmuma initialization.
-Nathan
On Sun, Jan 26, 2014 at 04:10:
Good point. Done.
On Jan 24, 2014, at 6:54 PM, Paul Hargrove wrote:
> Noticed the following in autogen output:
>
> === Patching configure for Sun Studio Fortran version strings (_F77)
>
> While probably harmless, my own inclination would be to apply as few patches
> to the generated configu
15 matches
Mail list logo
