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 53DE73857831; Thu, 10 Sep 2020 23:31:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 53DE73857831
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1599780675;
 bh=RL/FplcJvMmw4SfecS1SaW6NuX+l1+3al/db4upPJcQ=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=GuEcFrqPK6OeCTJYt8iUyWx9US1FMrx95xfVrUQvAawVP1T6D0X8rh0l7t+gNi9pD
 hsbQsJ7v5jeUjcm6DKjC+LbB+6x6DNgFw6llUKAPA7a6feO3XzzyQ5Zb68XfIBAQfL
 bJIP1+2CalohYX4mSHtbqbYBL9IFcpoptEEgWmQw=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96983] [11 regression] ICE compiling
 gfortran.dg/pr96711.f90 starting with r11-3042
Date: Thu, 10 Sep 2020 23:31:14 +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: 11.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-96983-4-IkmCfdQkS7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96983-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2020 23:31:15 -0000

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

--- Comment #18 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #17)
> const poly_uint16_pod mode_precision[NUM_MACHINE_MODES] =3D=20
> {
> ...
>   { 4 * BITS_PER_UNIT },   /* SF */
>   { 8 * BITS_PER_UNIT },   /* DF */
>   { 126 },                 /* KF */
>   { 127 },                 /* TF */
>   { 128 },                 /* IF */
> ...
>=20
> Why aren't KFmode, IFmode and TFmode all 128???   Mike?

This comes from rs6000-modes.h:

/* We order the 3 128-bit floating point types so that IFmode (IBM 128-bit
   floating point) is the 128-bit floating point type with the highest
   precision (128 bits).  This so that machine independent parts of the
   compiler do not try to widen IFmode to TFmode on ISA 3.0 (power9) that h=
as
   hardware support for IEEE 128-bit.  We set TFmode (long double mode) in
   between, and KFmode (explicit __float128) below it.

   We won't encounter conversion from IEEE 128-bit to IBM 128-bit because we
   don't have insns to support the IBM 128-bit aritmetic operations.  */

#ifndef RS6000_MODES_H
#define RS6000_MODES_H          1
#define FLOAT_PRECISION_IFmode  128
#define FLOAT_PRECISION_TFmode  127
#define FLOAT_PRECISION_KFmode  126=