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 F1C78385782B; Mon, 14 Sep 2020 19:04:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F1C78385782B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1600110287;
 bh=rJYCjAOwPGF1tI86P+MOwYvy/h3ri23B7ifieULybBc=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=DbU96pEwqZT50fA7QriD6FdcppvmJItPiB54QgGb4sL1umGtEz0Hnb5LmglGxcVN8
 uhx94eJwedc356zbI8UqTu0mmEPZc1ZBRa0qD4H9TZ9PbXQjHglOt9nFd39S7vjrAi
 Y2PO+4loglCRkm7e8G3XdMJGwAmQJctaealIw0hs=
From: "anlauf 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: Mon, 14 Sep 2020 19:04:47 +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: anlauf 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-PyA2IYvsgi@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 19:04:48 -0000

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

--- Comment #23 from anlauf at gcc dot gnu.org ---
(In reply to joseph@codesourcery.com from comment #22)
> Closely related: the LONG_DOUBLE_TYPE_SIZE target macro which assumes=20
> "size in bits" can uniquely determine the format of long double.  In the=
=20
> absence of hacks such as the above, LONG_DOUBLE_TYPE_SIZE needs replacing=
=20
> by a target hook that returns the machine mode, not "size in bits" (maybe=
=20
> a hook that covers all of float, double and long double).

Remember that Fortran needs a correspondence between a storage representati=
on
(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.=