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 D57A13851C17; Mon, 14 Sep 2020 20:42:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D57A13851C17
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1600116176;
 bh=vhzs/pLVVddbKJyedk69NL+gMLTi5/gi7jMaRB8kI/E=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=IzJkmnL7qmis/39QDpragCSz8Rqo0Jqh71ExPNBcw5Bsk2aA1aF+2cJe7XiKyGVGM
 WLiGlDGDzI+EV62o8Yna0xp94hE+5Wo+ICLsYTMfXQMS2RgVg6yqU+aYDnxnpc/+s7
 Nm7bw9GoifJ9mFHT/cxcyZ4USoF3MF8H2MmzUbCY=
From: "joseph at codesourcery dot com" <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: Mon, 14 Sep 2020 20:42:56 +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: joseph at codesourcery dot com
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-zWLwgkgill@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: Mon, 14 Sep 2020 20:42:56 -0000

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

--- Comment #25 from joseph at codesourcery dot com <joseph at codesourcery=
 dot com> ---
On Mon, 14 Sep 2020, anlauf at gcc dot gnu.org wrote:

> Remember that Fortran needs a correspondence between a storage representa=
tion
> (in bytes / bits) and the kind type on the language side.  We'd thus need=
 a
> method to get the machine mode for a given representation.  If there are
> multiple representations with the same storage size (ieee128 vs. ibm128),
> the ME needs to provide a way to the FE to uniquely address those.

What that suggests to me is having a target hook mapping a Fortran kind to=
=20
a floating-point machine mode (or to one of the global tree nodes for=20
floating-point types), alongside the target hook mapping a C type (float,=20
double, long double) to a machine mode.=