From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DFEF0386101D; Wed, 9 Sep 2020 19:03:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DFEF0386101D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1599678197; bh=se/JB3kguugCwFSfr/IYUtlXj7ii25QQPQ3hwqFz8fM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Jv+MnrBTrBsSMTWYcPhs7lA4bvzLvWq8fXMnzAI+pt+c4Vxw6Vqa0Yh8D19z41/AZ 6MOckHGjBAo2siykX0LTlVHiHHJj5qavEhzQJvRvDZAGwS6Xu/PTzbArNu+KCHolvV AE+fnxDwaKycssc7brFc0yjshlHwZzy8ZvEbiYzA= From: "bergner at gcc dot 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: Wed, 09 Sep 2020 19:03:17 +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: cc Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2020 19:03:18 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96983 Peter Bergner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner at gcc dot gnu.or= g, | |segher at gcc dot gnu.org --- Comment #11 from Peter Bergner --- (In reply to anlauf from comment #8) > There's apparently a real kind with mode_precision >=3D 128, > so we have to find out what it is, and if we can convert to it. To really confuse things, there are 2 16-byte float types on POWER. :-) Our old IBM double double format (__ibm128) and the newer IEEE128 format (__ieee128). We support using both types at the same time. Our "long doub= le" type (is that what fortran uses?) is set to one of those types, depending o= n a configure time option (...and maybe a compile time option?).=