From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9BF05385B836; Tue, 31 Mar 2020 14:36:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9BF05385B836 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585665411; bh=1O/wOynKm9oBUW9gCucx/3gd443OO4EhbbiJcPs9EN4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eQ+VWUxFfMlLtvHsKpzgvK+WukV2Po+hjHttXja1uOmaEt/xH6ER0NJ4JsnQvBJ6p PCt+XYjd5lWzPj95AQHcqLVM9A/bmAEa4EybBpN5hFF5PY+cbO6k5GPnpbQTqTX8+W 3wqbanEpr7WyDzMrFL0RlR4AWoU3W3GflRM9KM5M= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94420] [8/9/10 Regression] ICE error: insn does not satisfy its constraints Date: Tue, 31 Mar 2020 14:36:51 +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.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: segher at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 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: Tue, 31 Mar 2020 14:36:51 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94420 --- Comment #5 from Segher Boessenkool --- It is undefined behaviour to access such a register in any way -- sure, you *can* inspect it, there just is no guarantee at all what value you will get. It still is a useful thing to do in debug code and the like, of course.=