public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@arm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: binutils@sources.redhat.com, Nick Clifton <nickc@redhat.com>
Subject: Re: [rfa] ARM .cfi_* support
Date: Thu, 22 Apr 2004 17:02:00 -0000	[thread overview]
Message-ID: <1082652476.20833.25.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <20040422163114.GA32198@nevyn.them.org>

On Thu, 2004-04-22 at 17:31, Daniel Jacobowitz wrote:
> On Fri, Apr 09, 2004 at 05:01:42PM -0400, Daniel Jacobowitz wrote:
> > This has been kicking around in my tree for a while now.  It adds support
> > for the .cfi_* directives, using the standard or FPA registers - I didn't
> > bother adding any of the other coprocessor registers, since their numbering
> > is still a little unclear, and usually the general purpose registers are all
> > you need.
> > 
> > Tested on arm-elf.  OK?
> 
> Ping?

Sorry, missed this one (if you will post messages on a UK public
holiday...)

I think that we should be looking to move to the EABI DWARF register
numbers soon (http://www.arm.com/products/DevTools/abi/aadwarf.pdf).  I
would rather that we didn't introduce new uses of the old register
numbering schemes. 

R.

  reply	other threads:[~2004-04-22 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040409210142.GA31470@nevyn.them.org>
2004-04-22 16:32 ` Daniel Jacobowitz
2004-04-22 17:02   ` Richard Earnshaw [this message]
2004-04-22 17:37     ` Daniel Jacobowitz
2004-05-03 17:20       ` Daniel Jacobowitz
2004-09-19 15:37         ` Daniel Jacobowitz
2004-10-23 18:29       ` Daniel Jacobowitz
2004-10-25 12:28         ` Nick Clifton

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=1082652476.20833.25.camel@pc960.cambridge.arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=binutils@sources.redhat.com \
    --cc=drow@false.org \
    --cc=nickc@redhat.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).