Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: New function to supply only one x87 register
Date: Fri, 09 Feb 2001 05:47:00 -0000	[thread overview]
Message-ID: <s3izofwklxu.fsf@debye.wins.uva.nl> (raw)
In-Reply-To: <200102081828.NAA25559@indy.delorie.com>

Eli Zaretskii <eliz@delorie.com> writes:

> There's a strange asymmetry in i387-nat.c: i387_fill_fsave accepts a
> REGNO argument and can fill only one register's value, but
> i387_supply_fsave cannot.  I needed this to be symmetrical, but I
> didn't want to break existing APIs.  So I added a new function that
> handles one register only.  See below.

Hmm, the asymmetry you're seeing is the same asymmetry that exists
between supply_gregset() and fill_gregset().  Ultimately this
asymmetry stems from the fact that GDB's register cache is a
write-through cache (at least that's what I think).  This means that
it never hurts to supply the full FSAVE/FXSAVE info even if only one
register is requested, and that is what all other targets that use the
stuff from i387-nat.c do.  Is there a compelling reason you cannot do
the same in the go32 target?  I'd really prefer keeping the number of
interfaces as small as possible, and therefore I'd like to avoid
adding the i387_supply_fpreg function.

Mark

PS. Sorry for being so critical about your work.  I really don't want
    to discourage you.  Feel free to show me the code, if you don't
    know what to do with my suggestions.


  reply	other threads:[~2001-02-09  5:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 10:28 Eli Zaretskii
2001-02-09  5:47 ` Mark Kettenis [this message]
2001-02-09  6:59   ` Eli Zaretskii
2001-02-09  8:55     ` Mark Kettenis
2001-02-10  3:42       ` Eli Zaretskii
2001-02-10 14:59         ` Mark Kettenis
2001-02-16  9:33           ` 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=s3izofwklxu.fsf@debye.wins.uva.nl \
    --to=kettenis@wins.uva.nl \
    --cc=eliz@is.elta.co.il \
    --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