public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: richard.earnshaw@arm.com
Subject: Re: Patch to change ARM register name set
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <199906141438.PAA03661@sun52.NIS.cambridge> (raw)
In-Reply-To: <199906141409.PAA01497@pathia.cygnus.co.uk>

nickc@cygnus.com said:
>   Does anyone have any comments on the patch below ?  It changes the
>   ARM disassembler so that by default it uses the APCS register naming
>   scheme, rather than the ISA register naming scheme.  It also
>   introduces a new command line switch to objdump: -M or
> --target-data,
>   which takes an argument which can be processed in a target specific
>   manner.  If the target is the ARM then the text of the -M switch is
>   checked to see if it is a register name set selector
>   ("standard_names" or "apcs_names") and if so it chooses the
>   appropriate name set. 


Personally, I can't stand the APCS register names.  They seem illogical to 
me.  Added to this is the fact that certain APCS options are supposed to 
change the bindings of some names: for example r9 is sometimes known as 
either sb or v6 depending on the options supplied to the assembler; 
similarly r10 can be either sl or v7 (I think I even saw a situation once 
where r10 was called v6 because r9 was being used for sb, but r10 was not 
being used for sl).  In other words, it isn't even obvious if such names 
are static.

Thumb uses yet another set of aliases for some of these registers, due to 
the restrictions on accessing the high registers from many instruction 
formats.

Finally, I thought that there was already a command built into gdb that 
could change the register names to the apcs variant if desired; this can 
be put into an init script, so I see little point in the need for a 
command-line option to do this as well.

If we must add this, can't we make it part of the configuration options, 
then a target which uses the current convention doesn't change under 
people's feet.

Richard.

  parent reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor
1999-07-01  0:00 ` Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Richard Earnshaw
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Scott Bambrough
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Richard Earnshaw
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor

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=199906141438.PAA03661@sun52.NIS.cambridge \
    --to=rearnsha@arm.com \
    --cc=nickc@cygnus.com \
    --cc=richard.earnshaw@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).