From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 70DD43894C39; Mon, 12 Apr 2021 12:26:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 70DD43894C39 From: "mss at tutanota dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100041] ICE in curr_insn_transform, at lra-constraints.c:4022 Date: Mon, 12 Apr 2021 12:26:18 +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: 10.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mss at tutanota dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 12.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: Mon, 12 Apr 2021 12:26:18 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100041 --- Comment #21 from mss at tutanota dot de --- (In reply to Jakub Jelinek from comment #19) > I'm worried that there isn't enough time to find out before GCC11 release= if > some packages in the wild aren't using that option. > E.g. I wonder where it comes from in this PR. Clearly it doesn't come fr= om > gcc, so does it come from LLVM makefiles or has the reporter just added i= t? I was trying to build an LLVM for one of my machines from a much more power= ful machine and wanted to add the flags that `-march=3Dnative' enables for that processor but I was unaware that `-m128bit-long-double' was enabled by defa= ult already. I accidentally added `-m96bit-long-double' myself instead of `-m128bit-long-double', running g++ with both `-m64' and `-m96bit-long-doub= le' caused the ICE.=