From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4CCAE3858C3A; Fri, 29 Dec 2023 01:35:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4CCAE3858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1703813735; bh=w3x33mdvH1Yg7ZkfI0XjlyB3o/7qFUCF7GLTn20TTJU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LGE/DGc1yAzPGMRrbRp+61KM8f0rhOiqazopVTOcoa00ynMfqcnwaYdHR0NYHrrCL zR7+2usw5xBk1+oesBPVEMvcO+BeozeLwrr202TI3syVmrXQsogMjnIsfFUDc1vEsa ISWiR/zstbxmwlPn5YUc2PN5Qowi367AFkbY9aZQ= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/29869] sim: align sim register numbers with gdb register numbers Date: Fri, 29 Dec 2023 01:35:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: vapier at gentoo dot org X-Bugzilla-Target-Milestone: --- 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://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29869 --- Comment #5 from Tom Tromey --- The issue for gdbserver integration is that a general request may arrive, which just means "send all the registers". So, the server has to know how to iterate over them. Digging a bit I see this info in some ports, but it's not generically available via the sim public API. It works in gdb due to the synchronicity you point out: gdb and the sim generally agree (or there is a mapping). I don't really understand why this info isn't in the cgen model either, but it doesn't seem to be. Anyway I suspect a new field in _sim_cpu may be the way to go... Though looking at this, we also don't know the size of registers. gdb does, but it doesn't inform the remote of this -- the remote is expected to know. --=20 You are receiving this mail because: You are on the CC list for the bug.=