From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1ACA33851C31; Wed, 9 Sep 2020 17:58:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1ACA33851C31 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1599674299; bh=1bVg/ACdhk7GV+mA9djIrNH8+vlBdo4mEHviuZEjPhw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Pkb2wDff/ABhNDpYvuGP7oGl0IS8r26iGr75uTX/0B1ng7mKJsJLh0oiSmFzHJu8B rVk7G/jY0ZDIcDoYUy8ZOy1v82u2gwAVRylPeAKyQIx6eEm0gswBlXoIqlluji/r7W 2qFgMI4hn42JX9Ls+weJEyBLSYH4DXN1zRMbcCS0= From: "anlauf 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 17:58:19 +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: 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 17:58:19 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96983 --- Comment #10 from anlauf at gcc dot gnu.org --- (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #9) > >> 0x67606b build_round_expr > >> /vol/gcc/src/hg/master/local/gcc/fortran/trans-intrinsic.c:408 > > > > That's: > > > > arg =3D fold_convert (gfc_float128_type_node, arg); > > > > Can you find out what gfc_float128_type_node is on SPARC, > 408 arg =3D fold_convert (gfc_float128_type_node, arg); > (gdb) p gfc_float128_type_node > $2 =3D OK. Can you print kind which was determined a few lines before? Also, to find out why gfc_float128_type_node is NULL_TREE, can you investigate the array gfc_real_kinds? On x86, the supported kind values are 4,8,10,16, and (gdb) p gfc_real_kinds[3] $9 =3D {epsilon =3D {{_mpfr_prec =3D 113, _mpfr_sign =3D 1, _mpfr_exp =3D -= 111,=20 _mpfr_d =3D 0x27ee628}}, huge =3D {{_mpfr_prec =3D 113, _mpfr_sign = =3D 1, _mpfr_exp =3D 16384,=20 _mpfr_d =3D 0x27ee5e8}}, tiny =3D {{_mpfr_prec =3D 113, _mpfr_sign = =3D 1,=20 _mpfr_exp =3D -16381, _mpfr_d =3D 0x27ee5c8}}, subnormal =3D {{_mpfr_= prec =3D 113,=20 _mpfr_sign =3D 1, _mpfr_exp =3D -16493, _mpfr_d =3D 0x27ee608}}, kind= =3D 16, radix =3D 2,=20 digits =3D 113, min_exponent =3D -16381, max_exponent =3D 16384, range = =3D 4931, precision =3D 33,=20 mode_precision =3D 128, c_float =3D 0, c_double =3D 0, c_long_double =3D = 0, c_float128 =3D 1} In trans-types.c we have: if (gfc_real_kinds[index].c_float128) gfc_float128_type_node =3D type; Look in particular at the value of c_float128. > I'd expect that's long double, which is IEEE128 on SPARC. So if it is IEEE128, where does the difference from x86 come from?=