From: Richard Henderson <rth@twiddle.net>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] better alpha_register_virtual_type
Date: Mon, 02 Jun 2003 22:39:00 -0000 [thread overview]
Message-ID: <20030602223910.GD10655@twiddle.net> (raw)
In-Reply-To: <3EDBA02B.6090201@redhat.com>
On Mon, Jun 02, 2003 at 03:06:19PM -0400, Andrew Cagney wrote:
> >I thought it obvious to rename my existing hook, but that changes
> >the behaviour of "info r" -- I no longer get the pc decoded, and
> >indeed "ptype $pc" once again yields int64_t.
>
> Something weird is happening. The only thing notable about the d10v is
> that it doesn't set PC_REGNUM (per above, the d10v works). Perhaphs the
> alpha definition is confusing std-regs.c / builtin-regs.c (but that
> doesn't make much sense).
I have no idea. I can't replicate this now. I've made the
change to _register_type again and things seem to work as
expected. Perhaps I did something stupid before. *shrug*
r~
prev parent reply other threads:[~2003-06-02 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 5:04 Richard Henderson
2003-06-02 16:30 ` Daniel Jacobowitz
2003-06-02 16:43 ` Richard Henderson
2003-06-02 17:09 ` Daniel Jacobowitz
2003-06-02 19:06 ` Andrew Cagney
2003-06-02 22:39 ` Richard Henderson [this message]
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=20030602223910.GD10655@twiddle.net \
--to=rth@twiddle.net \
--cc=ac131313@redhat.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