[Bug fortran/67068] Ambiguous interfaces generated when including open mip fortran header

[Bug fortran/67068] Ambiguous interfaces generated when including open mip fortran header

[kargl at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67068

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Mike Glass from comment #0)
> Using gfortran-5.2.0 with openmpi 1.8.7 on a Linux RHEL system.
> 
> When compiling a FORTRAN file  with "-freal-4-real-8 -fdefault-double-8
> -fdefault-real-8"

What happens if you don't use the options?  You
did read the document for the -fdefault-* right?
Did you compile everything, and I mean everything,
with those options?

[Bug fortran/67068] Ambiguous interfaces generated when including open mip fortran header

[mwglass at sandia dot gov]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67068

--- Comment #2 from Mike Glass <mwglass at sandia dot gov> ---
Yes, all the FORTRAN code is compiled with those options. We want to mimic the
behavior of the Intel compiler when we add the '-r8' flag to their compiler:

Makes default real and complex declarations, constants, functions, and
intrinsics 8 bytes long. REAL declarations are treated as DOUBLE PRECISION
(REAL(KIND=8)) and COMPLEX declarations are treated as DOUBLE COMPLEX
(COMPLEX(KIND=8)). Real and complex constants of unspecified KIND are evaluated
in double precision (KIND=8).

[Bug fortran/67068] Ambiguous interfaces generated when including open mip fortran header

[sgk at troutmask dot apl.washington.edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67068

--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Jul 30, 2015 at 06:24:19PM +0000, mwglass at sandia dot gov wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67068
> 
> --- Comment #2 from Mike Glass <mwglass at sandia dot gov> ---
> Yes, all the FORTRAN code is compiled with those options. We want to mimic the
> behavior of the Intel compiler when we add the '-r8' flag to their compiler:
> 
> Makes default real and complex declarations, constants, functions, and
> intrinsics 8 bytes long. REAL declarations are treated as DOUBLE PRECISION
> (REAL(KIND=8)) and COMPLEX declarations are treated as DOUBLE COMPLEX
> (COMPLEX(KIND=8)). Real and complex constants of unspecified KIND are evaluated
> in double precision (KIND=8).
> 

You should only need -freal-4-real-8.  

If your code uses COMMON or EQUIVALENCE, you may also
want to use -finteger-4-integer-8

In addition, it is advisable to never mix the 
-fdefault-* and -freal-* options.  These do 
different things internally, and may in fact
cause conflicts.

[Bug fortran/67068] Ambiguous interfaces generated when including open mip fortran header

[anlauf at gmx dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67068

Harald Anlauf <anlauf at gmx dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gmx dot de

--- Comment #4 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Mike Glass from comment #2)
> Yes, all the FORTRAN code is compiled with those options. We want to mimic
> the behavior of the Intel compiler when we add the '-r8' flag to their
> compiler:
> 
> Makes default real and complex declarations, constants, functions, and
> intrinsics 8 bytes long. REAL declarations are treated as DOUBLE PRECISION
> (REAL(KIND=8)) and COMPLEX declarations are treated as DOUBLE COMPLEX
> (COMPLEX(KIND=8)). Real and complex constants of unspecified KIND are
> evaluated in double precision (KIND=8).

Is there a reason you don't "use mpi"?