Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Mark Kettenis <kettenis@science.uva.nl>, gdb-patches@sources.redhat.com
Subject: Re: RFA: i386 Linux: provide correct type for orig_eax register
Date: Mon, 14 Jan 2002 13:58:00 -0000	[thread overview]
Message-ID: <np6664mw4q.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3C40C94E.7060702@cygnus.com>


Andrew Cagney <ac131313@cygnus.com> writes:
> > I think we should #define HAVE_SSE_REGS unconditionally in
> >> config/i386/tm-linux.h.  Later, when things are properly multi-arched,
> >> we can decide whether we actually display thos registers based on the
> >> actual processor model.
> > Okay.  I'll give that a try.
> 
> 
> I'm trying to decide if it will break something.
> 
> The old ``remote packet is defined by the layout of the register
> buffer'' problem is lurking ready to strike :-(  This would put the
> SSE registers into the register buffer causing GDB to try to send them
> to a target that, rightly, doesn't expect them (hmm and also doesn't
> support a register-write packet)
> 
> It is why I was hacking on remote.c.  I've two more things to do: the
> protocol format command and sort out what ever happend to a
> read-register packet proposal that was posted.

Well, in that context, may I at least commit the change I posted?  It
simply extends the pattern of i386_linux_register_raw_size,
i386_linux_register_byte, and i386_linux_register_name.


  reply	other threads:[~2002-01-14 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 14:23 Jim Blandy
2002-01-12  5:13 ` Mark Kettenis
2002-01-12 15:14   ` Jim Blandy
2002-01-12 15:40     ` Andrew Cagney
2002-01-14 13:58       ` Jim Blandy [this message]
2002-01-14 14:31         ` Mark Kettenis

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=np6664mw4q.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.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