From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 53D99385E02A; Thu, 2 Apr 2020 12:32:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 53D99385E02A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585830727; bh=GwHtCxUqad/6obZhMAS3QlwCvqeWKVW6ermd5k7q9VE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=K2x12Q8tVTsGzA9f54Lh5RUyJTWUXpH7lWa1g0fxqlVOWgSOQmqgzYtDyUNGQd7jV 8rVcmxhWWtAG5QbY3gjxzDkSB6qgKFvakc49OB6EJTfop9G1WfpotRZpKWChJfmL2p Zd1yULKTWA7vzaXpUiBog0fOyznExFu3tFT9ADx4= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/93264] [10 Regression] ICE in cfg_layout_redirect_edge_and_branch_force, at cfgrtl.c:4522 Date: Thu, 02 Apr 2020 12:32:07 +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: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned 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: Thu, 02 Apr 2020 12:32:07 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93264 --- Comment #10 from Richard Biener --- Makes me wonder if hot/cold splitting should use a special jump instruction for crossing jumps which we could fixup/split very late so we see (parallel (set reg (label_ref ..)) (set pc (reg)) (clobber reg)) or something like that. That is, make sure the crossing jump, if indirect, has the destination computation easily accessible and replaceable.=