public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@cygnus.com>
To: richard.earnshaw@arm.com
Cc: binutils@sourceware.cygnus.com, 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: <199906141529.QAA01563@pathia.cygnus.co.uk> (raw)

Hi Richard,

: Personally, I can't stand the APCS register names.  They seem
: illogical to me.

I agree with you 100%.

: 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.

This option is so that other tools can also change the register name
set being used.  In particualr we have a customer who is insisting on
the APCS name set (fools) for things like objdump and Cygmon.
 
: 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.

No - it really needs to be a run time option.  However I am quite
happy to change it so that the standard names are the default and the
APCS names are only selected via a command line option.


Cheers
	Nick

             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 [this message]
1999-07-01  0:00 ` Scott Bambrough
  -- strict thread matches above, loose matches on Subject: below --
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor
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 ` Richard Earnshaw
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` Ian Lance Taylor
1999-07-01  0:00 ` Richard Earnshaw

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=199906141529.QAA01563@pathia.cygnus.co.uk \
    --to=nickc@cygnus.com \
    --cc=binutils@sourceware.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).