From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 059AF3857001; Mon, 27 Jul 2020 21:45:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 059AF3857001 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595886340; bh=y/yQLVFaorPijydK39MZp4viV9wZHoThW4uIXWRroDk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eVgmyoZPaLrLv7boAc3XFwR2jNXbkyclteXuBZzWzuFKMdX6uEtSM/d3i7zkLfR2L Uducmato1E1zh5KRBvB0DQuaitfXg38KodlE04xoqAJiOOMEzZ7AW5T0xChCPtrNxS iCBC9c5h0dWBEFLO2ZfG/zRVIRSM1I8DRPVtC3Ko= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/96343] LTO ICE on PPC64le Date: Mon, 27 Jul 2020 21:45:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.1.0 X-Bugzilla-Keywords: ice-on-valid-code, lto X-Bugzilla-Severity: normal X-Bugzilla-Who: segher 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: --- 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, 27 Jul 2020 21:45:40 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96343 --- Comment #3 from Segher Boessenkool --- Thanks for the report. Yes, not sure we can reproduce it like this. We might need something smaller, more self-contained. In the meantime... Can you check if this still happens with trunk, or with GCC 10? If it doesn't, we don't have to chase a bug that has been solved already, and we can bisect to find the patch that fixed this (hopefully actually fixed, it might be just a side effect). Or, if it is still occurring, it is something we need to know as well :-)=