Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Luis Machado <luis.machado@linaro.org>,
	Richard Earnshaw	<Richard.Earnshaw@arm.com>
Cc: Christian Biesinger <cbiesinger@google.com>,
	"gdb-patches\\@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH] Add a comment for the ARM_F{0..7}_REGNUM registers
Date: Tue, 11 Feb 2020 09:20:00 -0000	[thread overview]
Message-ID: <73905855-549A-4BA8-9E6B-F9D567E3E2AC@arm.com> (raw)
In-Reply-To: <3a393049-bc2d-b8be-1b47-20114311d5b3@linaro.org>



> On 11 Feb 2020, at 00:32, Luis Machado <luis.machado@linaro.org> wrote:
> 
> On 2/10/20 8:35 PM, Christian Biesinger via gdb-patches wrote:
>> These are for the obsolete FPA architecture.
>> gdb/ChangeLog:
>> 2020-02-10  Christian Biesinger  <cbiesinger@google.com>
>> 	* arch/arm.h (enum gdb_regnum): Add comment for the FP0..7
>> 	registers.
>> Change-Id: I6920616318ee637493d4ca12b91fa2ebcd103d76
>> ---
>>  gdb/arch/arm.h | 1 +
>>  1 file changed, 1 insertion(+)
>> diff --git a/gdb/arch/arm.h b/gdb/arch/arm.h
>> index 13f030af82..2d9e87eb42 100644
>> --- a/gdb/arch/arm.h
>> +++ b/gdb/arch/arm.h
>> @@ -31,6 +31,7 @@ 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.  */
>>    ARM_F0_REGNUM = 16,		/* first floating point register */
>>    ARM_F3_REGNUM = 19,		/* last floating point argument register */
>>    ARM_F7_REGNUM = 23, 		/* last floating point register */
> 
> This looks obvious enough. cc-ed Alan in case he has any thoughts.

I’m happy for that to be pushed as is. But...

My only problem here is the use of the word “obsolete”. If it’s obsolete, why are
we still supporting it?

Digging into it, I didn’t realise FPA was quite that old, but it dates back to around 1995.

Some good background information here (question was asked only 22 days ago!)
https://retrocomputing.stackexchange.com/questions/13400/history-of-arm-linux-and-fpa

GCC support for FPA was removed back in 2012, in GCC 4.8.
And GDB has a history of removing features after GCC support has been removed.

I’d suggest it’s worth someone ripping out FPA support entirely in a follow on set of
patches. This leaves us with vfpv2, vfpv3, xscale-iwmmxt and no float.

(cc-ing Richard who removed the FPA from GCC, on the off chance he has any objections).

Alan.

  reply	other threads:[~2020-02-11  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 23:36 Christian Biesinger via gdb-patches
2020-02-11  0:32 ` Luis Machado
2020-02-11  9:20   ` Alan Hayward [this message]
2020-02-11 16:29     ` Christian Biesinger via gdb-patches

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=73905855-549A-4BA8-9E6B-F9D567E3E2AC@arm.com \
    --to=alan.hayward@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=nd@arm.com \
    /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