From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>,
colins@google.com, gdb-patches@sources.redhat.com
Subject: Re: re-ordered i386 regcache
Date: Wed, 30 Apr 2003 18:20:00 -0000 [thread overview]
Message-ID: <20030429152529.GA28812@nevyn.them.org> (raw)
In-Reply-To: <3EAE9847.90809@redhat.com>
On Tue, Apr 29, 2003 at 11:20:39AM -0400, Andrew Cagney wrote:
> >All three require a projection such that, assumed contigious, debug info
> >>registers project onto raw registers. Isn't this what i386 has?
> >
> >
> >I don't think so. All three need a view of registers slightly
> >different from the "normal" one, but they don't have "assumed
> >contiguous debug info registers". In fact in e500 they're assumed
> >not-contiguous.
>
> Please study the code. A 32 bit MIPS ABI on a 64 bit MIPS represents
> long long as two 32 bit sub-parts of two 64 bit registers; the two 32
> bit parts are assumed to be adjacent.
>
> The adjacent assumption will eventually be lifted, but that will be done
> by someone implementing something like location descriptions.
I posit that this is the exact same problem as the i386 is currently
facing.
Remember, location descriptions come from the debug reader, not from
the target. Where do you think these hypothetical descriptors to tell
us which two registers the long long value occupies will come from?
Current debug info won't give them to us.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-29 15:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:27 patch for printing 64-bit values in i386 registers; STABS format Colin Smith
2003-04-25 2:07 ` Daniel Jacobowitz
2003-04-25 22:18 ` Mark Kettenis
2003-04-25 22:24 ` Daniel Jacobowitz
2003-04-26 3:05 ` Andrew Cagney
2003-04-26 3:20 ` Daniel Jacobowitz
2003-04-26 3:32 ` Andrew Cagney
2003-04-26 3:39 ` Daniel Jacobowitz
2003-04-26 8:25 ` Andrew Cagney
2003-04-27 3:47 ` Daniel Jacobowitz
2003-04-28 15:22 ` Mark Kettenis
2003-04-28 16:09 ` Andrew Cagney
2003-04-28 16:14 ` Daniel Jacobowitz
2003-04-28 16:15 ` Andrew Cagney
2003-04-28 16:37 ` Daniel Jacobowitz
2003-04-28 19:26 ` Andrew Cagney
2003-04-28 22:47 ` Daniel Jacobowitz
2003-04-29 2:15 ` re-ordered i386 regcache Andrew Cagney
2003-04-29 4:45 ` Daniel Jacobowitz
2003-04-29 14:30 ` Andrew Cagney
2003-04-29 15:08 ` Daniel Jacobowitz
2003-04-29 15:25 ` Andrew Cagney
2003-04-30 3:37 ` Daniel Jacobowitz
2003-04-30 14:28 ` Andrew Cagney
2003-04-30 18:20 ` Daniel Jacobowitz [this message]
2003-04-28 20:06 ` Re: patch for printing 64-bit values in i386 registers; STABS format Colin Smith
2003-04-28 0:51 ` Mark Kettenis
2003-04-28 16:18 ` Andrew Cagney
2003-04-28 17:30 ` Daniel Jacobowitz
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=20030429152529.GA28812@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=colins@google.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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