From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 00797385DC1B; Wed, 15 Apr 2020 20:05:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 00797385DC1B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586981134; bh=HSSZfRRr4w3EQx7rStsPYiqYkiQcmrT5acpXhybA8fM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Yt8vQI7Bt6GHIrkEpY6ieobKIqppVBFlnkL5Rcaym2InUTuv6rjYCeJCVAnJ6yC3h ndzcZbSPO9SeHTKXjkk5a5jf4fmLTGjohKMINh5QUIQTywOSGm0fWrBaX1zwoNUJRu +VNLrSE+YxBdIyLY5dUl5r0TiQlMlNgPHgaiSW9E= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/93974] [10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762 Date: Wed, 15 Apr 2020 20:05:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 9.2.1 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.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, 15 Apr 2020 20:05:34 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93974 --- Comment #21 from Peter Bergner --- (In reply to Jakub Jelinek from comment #20) > Have you managed to make some progress? This is one of the last 10 P1 > blockers of the release. I'm still working on it. I have a patch that fixes the issue, but I'm not = sure yet whether it's the "right" patch. Hopefully I'll know soon.=