Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@kettenis.dyndns.org>
To: jimb@zwingli.cygnus.com
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: i386 Linux: provide correct type for orig_eax register
Date: Mon, 14 Jan 2002 14:31:00 -0000	[thread overview]
Message-ID: <200201142231.g0EMV3Q00393@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <np6664mw4q.fsf@zwingli.cygnus.com> (message from Jim Blandy on 14 Jan 2002 16:59:49 -0500)

   From: Jim Blandy <jimb@zwingli.cygnus.com>
   Date: 14 Jan 2002 16:59:49 -0500

   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)

The new orig_eax register isn't in any publically released version of
GDB yet.  And actually I think your worries about the remote packet is
actually an argument to try to keep the remote packet the same for all
Linux targets.  Right now it will depend on the header files installed
on the system where GDB is built.

   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.

I'd really prefer the unconditional #define of HAVE_SSE_REGS.

Mark


      reply	other threads:[~2002-01-14 22:31 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
2002-01-14 14:31         ` Mark Kettenis [this message]

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=200201142231.g0EMV3Q00393@elgar.kettenis.dyndns.org \
    --to=kettenis@kettenis.dyndns.org \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@zwingli.cygnus.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