From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 22FDE385E00E; Sat, 28 Mar 2020 22:28:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 22FDE385E00E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585434484; bh=nHqDJyThdJwH19EtXOVQJH2UBSO5pTcDDqs9P5rKMtY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PHme0s8pDMpwwYKZRiIDiTKIjp/IzYINuB8d16BkuxPjRlvLkh2zoL+euH3dM2OTC u95kqE+ajs9p0bHdaDq+6XGKqqVGV83hNX8DvL5Nirk9B181F8oY/XSkFy8ZWjsKXD /xaEthJjrb7ys4gWeQuEFYTy8WRHFX8Yj1Iq/Qp8= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/87163] ICE in extract_insn, at recog.c:2305 Date: Sat, 28 Mar 2020 22:28:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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: Sat, 28 Mar 2020 22:28:04 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D87163 --- Comment #10 from Peter Bergner --- (In reply to Segher Boessenkool from comment #9) > So what causes this TF vs. IF? Cross and native should be exactly the sa= me, > but perhaps there is a difference in the configurations you have for the = two? Maybe on native, our long double defaults to IBM long double and on a cross build we somehow default to IEEE float 128? I wonder if the native build I= CEs when using -mfloat128 -mabi=3Dieeelongdouble ?=