From: Andrew Cagney <ac131313@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] remove ALPHA_FP_REGNUM
Date: Sun, 01 Jun 2003 19:08:00 -0000 [thread overview]
Message-ID: <3EDA4F16.30207@redhat.com> (raw)
In-Reply-To: <20030601185441.GA4652@twiddle.net>
> Even worse than other ports, this was some bogus non-architectural
> register that sort of corresponds to the dwarf2 CFA concept, but
> hasn't actually been set to anything useful in who knows how long.
>
> So I've removed it entirely. Ok?
Almost.
> * alpha-tdep.h (ALPHA_NUM_REGS): Decrement.
> (ALPHA_FP_REGNUM): Remove.
> (ALPHA_UNIQUE_REGNUM): Decrement.
> * alpha-tdep.c (alpha_register_name): Remove vfp entry.
> (alpha_cannot_fetch_register): Remove ALPHA_FP_REGNUM.
> (alpha_cannot_store_register): Likewise.
> * alphabsd-nat.c (fetch_inferior_registers): Don't set FP_REGNUM.
> * alpha-nat.c (supply_gregset): Likewise.
> * alphanbsd-tdep.c (fetch_core_registers): Likewise.
> Index: alpha-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
> retrieving revision 1.91
> diff -c -p -d -u -r1.91 alpha-tdep.c
> --- alpha-tdep.c 1 Jun 2003 18:44:13 -0000 1.91
> +++ alpha-tdep.c 1 Jun 2003 18:45:24 -0000
> @@ -57,7 +57,7 @@ alpha_register_name (int regno)
> "f8", "f9", "f10", "f11", "f12", "f13", "f14", "f15",
> "f16", "f17", "f18", "f19", "f20", "f21", "f22", "f23",
> "f24", "f25", "f26", "f27", "f28", "f29", "f30", "fpcr",
> - "pc", "vfp", "unique",
> + "pc", "unique"
> };
"vfp" should be replaced with "" leaving a hole in the register space.
Otherwize the layout of the remote protocol buffer gets changed and
doing that breaks compatibility with existing remote alpha targets (yes,
this shouldn't happen).
Otherwize ok.
Andrew
next prev parent reply other threads:[~2003-06-01 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 18:54 Richard Henderson
2003-06-01 19:08 ` Andrew Cagney [this message]
2003-06-01 19:10 ` Richard Henderson
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=3EDA4F16.30207@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@twiddle.net \
/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