From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Fix busted logic in find_saved_register()
Date: Sat, 20 Apr 2002 17:00:00 -0000 [thread overview]
Message-ID: <3CC20106.1080508@cygnus.com> (raw)
In-Reply-To: <20020420162639.X1627@dr-evil.shagadelic.org>
> Ok, I will commit the fix.
>
> > You mention that the alpha is calling that function. Is that directly
> > or indirectly? I'm going to eliminate the MIPS direct call.
>
> Directly. The alpha_get_saved_register() is nearly identical to the
> mips_get_saved_register().
If you've implemented INIT_SAVED_REGS() do you need a custom
get_saved_register()?
> How are you changing the MIPS target?
Things will affect the MIPS at two levels.
Ref:
Andrew Cagney - [rfc] Frame based register cache / frame->unwind
http://sources.redhat.com/ml/gdb/2002-04/msg00245.html
I'm looking to change the way frames are unwound. I'd ignore that patch
as posted - I've managed to greatly simplify things. Main thing to note
that the new code doesn't use find_saved_register(). Instead it uses a
recursive frame->register_unwind() method.
If/when this change goes through, any code using the existing
find_saved_register() would be handed a local copy.
--
At a more theoretical [sp] level, I'm looking to rewrite the entire
function. Much of the MIPS complexity comes about because its REGNUM's
are overloaded. For instance, the hardware fp0 register might be 64
bits but when a program (via debug info) refers to it, it is only 32 bits.
I think the way to handle this is to map debug info REGNUMs onto the
pseudo address space and then use register_{read,write} to map them onto
the corresponding hardware register.
This one is more theoretical as the SH5 is the first port to try to get
this working and (apparently) it flushed out a few teething problems.
enjoy,
Andrew
next prev parent reply other threads:[~2002-04-21 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 14:48 Jason R Thorpe
2002-04-20 16:08 ` Andrew Cagney
2002-04-20 16:26 ` Jason R Thorpe
2002-04-20 17:00 ` Andrew Cagney [this message]
2002-04-20 18:54 ` Jason R Thorpe
2002-04-20 22:35 ` Andrew Cagney
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=3CC20106.1080508@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.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