Hi,
it seems that the problem results from a compiler bug, because today I was
able to build the package with the compilers from "Intel Parallel Studio XE
2018" and "Portland Group Community Edition 2018". Unfortunately, I have no
contact person at Oracle to report the bug, so that it can be fixe
The bindings in v3.1.0 are incorrect. They are missing the asynchronous
attribute. That will be fixed in v3.1.1.
> On Jun 6, 2018, at 12:06 PM, Siegmar Gross
> wrote:
>
> Hi Jeff,
>
>> I asked some Fortran gurus, and they don't think that there
>> is any restriction on having ASYNCHRONOUS
Hi Jeff,
I asked some Fortran gurus, and they don't think that there
is any restriction on having ASYNCHRONOUS and INTENT on the
same line. Indeed, Open MPI's definition of MPI_ACCUMULATE
seems to agree with what is in MPI-3.1.
Is this a new version of a Fortran compiler that you're
using, per
Siegmar --
I asked some Fortran gurus, and they don't think that there is any restriction
on having ASYNCHRONOUS and INTENT on the same line. Indeed, Open MPI's
definition of MPI_ACCUMULATE seems to agree with what is in MPI-3.1.
Is this a new version of a Fortran compiler that you're using, p
I put in a PR to "fix" this but if you look at the standard it has both
intent(in) and asynchronous. Might be a compiler problem?
-Nathan
> On Jun 6, 2018, at 5:11 AM, Siegmar Gross
> wrote:
>
> Hi,
>
> I've tried to install openmpi-master-201806060243-64a5baa on my "SUSE Linux
> Enterprise
Hi,
I've tried to install openmpi-master-201806060243-64a5baa on my "SUSE Linux
Enterprise Server 12.3 (x86_64)" with Sun C 5.15 (Oracle Developer Studio
12.6). Unfortunately I still get the following error that I already reported
on April 12th and May 5th.
loki openmpi-master-201806060243-64a5b
