From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: RFC: Variables in blocks of registers
Date: Sun, 02 Feb 2003 16:27:00 -0000 [thread overview]
Message-ID: <20030202162746.GA27502@nevyn.them.org> (raw)
In-Reply-To: <3E3D43E5.3060904@redhat.com>
On Sun, Feb 02, 2003 at 11:14:29AM -0500, Andrew Cagney wrote:
> If only it were that easy. The dwarf2 reader, for instance, also
> contains the assumption that registers are allocated sequentially.
>
> Is the proposal to modify such readers so that they check against this
> next_allocated_regnum algorithm?
Where? I can't find this; it doesn't even acknowledge multi-register
values.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-02 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 14:48 Mark Kettenis
2003-02-01 15:48 ` Andrew Cagney
2003-02-01 17:09 ` Daniel Jacobowitz
2003-02-01 20:45 ` Andrew Cagney
2003-02-02 16:13 ` Mark Kettenis
2003-02-02 5:21 ` Daniel Jacobowitz
2003-02-02 16:52 ` Andrew Cagney
2003-02-02 16:27 ` Daniel Jacobowitz [this message]
2003-02-04 2:31 ` Jim Blandy
2003-02-04 4:07 ` Daniel Berlin
2003-02-02 15:33 ` Daniel Berlin
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=20030202162746.GA27502@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@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