The INTEGER*n, LOGICAL*n, REAL*n, etc., syntax has never been legal Fortran.
Fortran originally had only INTEGER, REAL, DOUBLE PRECISION, and COMPLEX
numeric types. Fortran 90 added the notion of a KIND of numeric, but left
unspecified the mapping of numeric KINDs to processor-specific storage
On Oct 14, 2015, at 5:53 PM, Vladimír Fuka wrote:
>
>> As that ticket notes if REAL*16 <> long double Open MPI should be
>> disabling redutions on MPI_REAL16. I can take a look and see if I can
>> determine why that is not working as expected.
>
> Does it really need to be just disabled when the
> As that ticket notes if REAL*16 <> long double Open MPI should be
> disabling redutions on MPI_REAL16. I can take a look and see if I can
> determine why that is not working as expected.
Does it really need to be just disabled when the `real(real128)` is
actually equivalent to c_long_double? Wou
On Wed, Oct 14, 2015 at 02:40:00PM +0100, Vladimír Fuka wrote:
> Hello,
>
> I have a problem with using the quadruple (128bit) or extended
> (80bit) precision reals in Fortran. I did my tests with gfortran-4.8.5
> and OpenMPI-1.7.2 (preinstalled OpenSuSE 13.2), but others confirmed
> this beha
Hello,
I have a problem with using the quadruple (128bit) or extended
(80bit) precision reals in Fortran. I did my tests with gfortran-4.8.5
and OpenMPI-1.7.2 (preinstalled OpenSuSE 13.2), but others confirmed
this behaviour for more recent versions at
http://stackoverflow.com/questions/3310904
