The following is seen on my Solaris-11.2 (but not 11.1) system.
It is present with the Studio compilers (at least 12.4 and 12.3) for both
32- and 64-bit targets.
It is also present with the Gnu compiler for 64-bit targets (with 32-bit
the build dies for a different reason).
FCLD libmpi_mpifh
I have a systems running Solaris 11.1 on x86-64 hardware and 11.2 in an
x86-64 VM.
To the extent I have tested the results are the same on both, despite
gcc-4.5.2 vs 4.8.2
I have normally tested only the Sun/Oracle Studio compilers on these
systems.
However, today I gave the vendor-provided gcc, g
Initial heads-up:
I appear unable to build on Solaris 11 on x86-64 using two different GNU
compilers (Studio compilers are fine).
This is a configuration I had not tried before, and I now find that the
1.8.8 release fails to build in the same way.
More details to follow...
-Paul
On Fri, Aug 14,
Usual place:
http://www.open-mpi.org/software/ompi/v1.10/
Barring any discovered issues, we will release after the OMPI telecon next
Tues (Aug 18)
Ralph
Another issue, maybe a little bit more unsettling.
If I iterate over the existing pvars, and for each after retrieving their
name I use the name to search for the associated index I get an error. A
short example is below.
George.
err = MPI_T_pvar_get_num(&numPvar);
if(err) MPI_Abort(M
For this particular test I used the current master (022a9d8).
I reread the MPI_T chapter and [as usual] there might be something that
cautions the current behavior (aka. returning MPI_T_ERR_INVALID_INDEX for
an index smaller than the number of cvars returned by MPI_T_cvar_get_num).
This is indicat
George: what OMPI version did you test?
> On Aug 14, 2015, at 2:14 PM, George Bosilca wrote:
>
> This user email requires special attention, as it highlighted some issues
> with our MPI_T variables.
>
> I wrote a short application to list all pvar and cvar available.
> Unexpectedly, listing t
This user email requires special attention, as it highlighted some issues
with our MPI_T variables.
I wrote a short application to list all pvar and cvar available.
Unexpectedly, listing the cvars leads to a lot of failures, 138 over 1035
cvars. If a cvar is broken I would have expected (based on
Paul,
i made PR #809 for the master https://github.com/open-mpi/ompi/pull/809
and for the branches :
- https://github.com/open-mpi/ompi-release/pull/504
- https://github.com/open-mpi/ompi-release/pull/505
- https://github.com/open-mpi/ompi-release/pull/503
Ralph,
since that can be seen as urgen
