From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 567DE385DC11; Wed, 1 Apr 2020 15:58:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 567DE385DC11 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585756726; bh=/zviQ+7kc09FFBfn7BGU6oobHf4VzLsgnLUeBz3bd2g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ECQH2nx5AwvBhzLew/ktbyxsjDZLcM80yqMnOURcf//tiljfSzTsct29jhv7ayuZf ZmEg22X3YiGA/OR6JiyHKyBEM3rNM8r6KhpJEVNk6tDiPtle1LM/JMMEFl7lkgl8qJ gpUUZD57Rm8GzdfcDEx2tmPf+OduE8kug/rt2NgQ= 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, 01 Apr 2020 15:58:45 +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, 01 Apr 2020 15:58:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93974 --- Comment #17 from Peter Bergner --- (In reply to Jakub Jelinek from comment #16) > Any progress? I'm sorry, I've been swamped with other things. Even so, given this (up to= now latent) bug has been there a while, and any patch here will affect all other architectures, do we really want to patch this area so close to the release= ?=20 Using -O2 is a workaround.=