From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] builtin-regs buglet
Date: Mon, 13 May 2002 09:27:00 -0000 [thread overview]
Message-ID: <200205131627.RAA25947@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Mon, 13 May 2002 12:22:35 EDT." <3CDFE84B.3040306@cygnus.com>
> > * builtin-regs.c (value_of_builtin_reg): Correctly calculate the
> > builtin reg number.
>
> Oops! Yes.
Installed.
>
> Want to live dangerously? Try setting fp_regnum to -1. It should
> [finally] fix the $fp (regname) vs $fp (info registers) problem.
Hmm, one step at a time... My current patch to for the arm is already
looking somewhat jumbo like. Unfortunately, I don't really see how I can
break it down, since the changes are all fairly fundamental.
R.
next prev parent reply other threads:[~2002-05-13 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 9:04 Richard Earnshaw
2002-05-13 9:22 ` Andrew Cagney
2002-05-13 9:27 ` Richard Earnshaw [this message]
2002-05-14 17:34 ` Andrew Cagney
2002-05-15 1:52 ` Richard Earnshaw
2002-05-18 14:24 ` Andrew Cagney
2002-05-19 7:50 ` 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=200205131627.RAA25947@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.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