From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5CFDE3858C83; Wed, 15 Mar 2023 16:55:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CFDE3858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678899341; bh=lHpCLuydx2u4TDh80/9v3s39qRNf5QZ4B6bXMBKziKo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ynkn+6u54GETD63dKNgiwcHk5ewXcgxKbhrZ1+WCfMNNSJ4sI0cCzqmOa5Q+Zr/GJ 8V6mwm7s1COA/RGizEa8v7M3lp0cacJPqw+tdBI1UGplWikUaPlh4X9G0tZ0rA7P1h mort5+NQdvpHmF6vXSnkrdYgqdHr02m1aMyJO5Nw= From: "luis.machado at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug tdep/23408] [aarch64] tui rename cpsr to pstate Date: Wed, 15 Mar 2023 16:55:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tdep X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: luis.machado at arm dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D23408 Luis Machado changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luis.machado at arm dot com --- Comment #9 from Luis Machado --- I don't think it would be a good idea. Yes, cpsr would be best named as pst= ate, but debugging stubs have been following what gdb advertises for a while now. We'd need to keep looking for cpsr and translate it to pstate. If there are scripts/automation out there looking for a register name of cp= sr, it will no longer work. --=20 You are receiving this mail because: You are on the CC list for the bug.=