From: Eli Zaretskii <eliz@is.elta.co.il>
To: Nick Duffek <nsd@redhat.com>
Cc: kettenis@wins.uva.nl, gdb@sources.redhat.com
Subject: Re: Register cache
Date: Sun, 11 Feb 2001 23:26:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010212092158.12969C-100000@is> (raw)
In-Reply-To: <200102112013.f1BKDpM11302@rtl.cygnus.com>
On Sun, 11 Feb 2001, Nick Duffek wrote:
> >Therefore I propose to make this "official" and change
> >the comment on target_fetch_registers() to:
> >
> > /* Fetch at least register REGNO, or all regs if REGNO == -1. */
>
> I think that's a great idea.
>
> >Another question is whether we should make this behaviour (I mean
> >having target_fetch_registers() supply all registers it managed to get
> >in one go) recommended practice.
>
> I don't agree with that. There are times when GDB just needs one
> register, and it may be much more efficient on some targets to fetch one
> register than to fetch all of them.
So you are telling, in effect, that it's okay to have
i387_supply_fsave get all the FP registers, and x86 targets which
don't like that should provide ther own code instead of using
i387_supply_fsave?
next prev parent reply other threads:[~2001-02-11 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-10 14:37 Mark Kettenis
2001-02-11 12:07 ` Nick Duffek
2001-02-11 23:26 ` Eli Zaretskii [this message]
2001-02-12 9:46 ` Nick Duffek
2001-02-12 10:37 ` Eli Zaretskii
2001-02-16 15:21 ` Mark Kettenis
2001-02-17 0:28 ` Eli Zaretskii
2001-02-17 3:19 ` Mark Kettenis
2001-02-13 13:38 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2000-08-31 5:50 Register Cache Peter Reilley
2000-08-24 17:01 Wrong PC after external interrupt Fabrice Gautier
2000-08-29 18:01 ` Register Cache Steven Johnson
2000-08-30 21:40 ` Steven Johnson
2001-03-26 6:46 ` Andrew Cagney
2001-03-26 7:22 ` Fernando Nasser
[not found] ` <3ABFD062.17EDADAF@neurizon.net>
2001-03-29 16:27 ` Andrew Cagney
2001-03-29 16:27 ` Fernando Nasser
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=Pine.SUN.3.91.1010212092158.12969C-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
--cc=nsd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).