From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id D8ECC3851C0C; Fri, 12 Jun 2020 04:16:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D8ECC3851C0C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1591935413;
 bh=5Kxw3llHepd6ZMXzt9e9/btTrQ1UT0hhzKR9gxRoJ/0=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=iFBk/4d9XjLmkNmq2yzRoDp0Oj78D3jpRGGqnbBdPBQ6I3Qbfu285IjhD/f/a9xgs
 R8y2cU44DX8rWkvXK2pmc69qTD4rY3Ww7CSEEgN53ZFXNsJdrrgJzMuVcRfEOr3jfu
 V3FTFx76CyoQl3IFW8kB27SqkQGQzFoN6LaA2tb4=
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95640] gfortran ieee_selected_real_kind returns 10
Date: Fri, 12 Jun 2020 04:16:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-95640-4-ahWcLz2pek@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2020 04:16:54 -0000

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

--- Comment #12 from kargl at gcc dot gnu.org ---
(In reply to Bill Long from comment #11)
> I checked with the Intel docs and the ia64 version of the compiler (what =
HPC
> users use) does not support x87.=20
>=20
> Is there a gfortran compiler option to disable x87 use (i.e. REAL(10) is =
an
> error), to match the other compilers?

The types are set up in trans-type.c(gfc_init_kinds).  I
do not see an option that would disable querying for=20
long_double_type_node.  In principle, one might be able
to define an option that prevents gfortran from see a
long_double_type_node. This should then disable REAL(10).

Looking at configure options, there is a --with-long-double-128
option but I've never used it.  Don't know if it will disable
REAL(10).  It appears linux specific.=