public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Luis Machado <luis.machado@arm.com>,
	Pedro Alves <pedro@palves.net>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] [Arm] Remove dead FPA code
Date: Tue, 4 Oct 2022 10:08:02 -0700	[thread overview]
Message-ID: <73479562-ab47-dfbf-aadc-7a2203c0f0e4@FreeBSD.org> (raw)
In-Reply-To: <dabad50a-5a0c-4661-6c94-9ac1ce784786@arm.com>

On 10/4/22 1:43 AM, Luis Machado via Gdb-patches wrote:
> On 10/3/22 20:16, Pedro Alves wrote:
>> On 2022-09-20 1:30 p.m., Luis Machado via Gdb-patches wrote:
>>
>>> diff --git a/gdb/arch/arm.h b/gdb/arch/arm.h
>>> index 36757493406..74a6ba93bc7 100644
>>> --- a/gdb/arch/arm.h
>>> +++ b/gdb/arch/arm.h
>>> @@ -44,11 +44,6 @@ enum gdb_regnum {
>>>      ARM_SP_REGNUM = 13,		/* Contains address of top of stack */
>>>      ARM_LR_REGNUM = 14,		/* address to return to from a function call */
>>>      ARM_PC_REGNUM = 15,		/* Contains program counter */
>>> -  /* F0..F7 are the fp registers for the (obsolete) FPA architecture.  */
>>
>> Shouldn't we leave behind a comment explaining why there's a hole between 15 and 25?
> 
> I pondered about this a bit more, and I think we should close the gap and bring CPSR down to
> 16, its "natural" position. It is what linux uses for user_regs as well, in gdb/arch/arm-linux.h:
> 
> /* The index to access CSPR in user_regs defined in GLIBC.  */
> #define ARM_CPSR_GREGNUM 16
> 
>>
>> IIRC the numbers can't be changed since we need to handle the case when the target
>> doesn't send an xml tdesc, so it'd be good to help future readers understand why
>> there's a hole.
> 
> That's correct. Though a 32-bit Arm target that doesn't support XML descriptions these days is not very
> common. I haven't seen one in a while.
> 
> I'm willing to declare old 32-bit Arm targets that don't send XML target descriptions back as unsupported.
> 
> To that effect, I suppose we should add a note to make it more explicit.
> 
> More below.

FWIW, the GDB stub in FreeBSD's kernel does not use XML target descriptions
for any architectures, but it also only tends to do GPRs and not any floating
point.  For 32-bit ARM it does not report any register values higher than
number 15 (PC), so it would not be affected by changing this.

Do you know if LLDB supports floating-point registers on 32-bit arm as well?
The register numbers in the 'g' packet are effectively part of the protocol
shared between the two, so might be worth coording with lldb folks as well if
they support FPA?

-- 
John Baldwin

  reply	other threads:[~2022-10-04 17:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 12:30 Luis Machado
2022-09-20 12:47 ` Eli Zaretskii
2022-10-02 13:39 ` Enze Li
2022-10-03  8:27   ` Luis Machado
2022-10-03 17:33 ` John Baldwin
2022-10-03 19:16 ` Pedro Alves
2022-10-04  8:43   ` Luis Machado
2022-10-04 17:08     ` John Baldwin [this message]
2022-10-04 17:43       ` Luis Machado
2022-10-04 21:36         ` John Baldwin
2022-10-05  8:26           ` Luis Machado
2022-10-05  8:36             ` David Spickett
2022-10-05  8:36               ` David Spickett
2022-10-05 16:48             ` John Baldwin
2022-10-05 16:57               ` Richard Earnshaw
2022-10-06 13:02                 ` Luis Machado
2022-10-10 14:58             ` Pedro Alves
2022-10-13  7:23               ` Luis Machado
2022-10-13  8:29                 ` Pedro Alves
2022-10-13  9:40                   ` Luis Machado
2022-10-25 13:54                     ` Luis Machado
2022-11-14 14:30                     ` Simon Marchi
2022-10-10 14:56     ` Pedro Alves
2022-10-13  7:18       ` Luis Machado
2022-10-13  8:44         ` Pedro Alves
2022-10-13  9:15           ` Luis Machado

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73479562-ab47-dfbf-aadc-7a2203c0f0e4@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=pedro@palves.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).