Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: aristovski@qnx.com
Cc: gdb-patches@sources.redhat.com, brobecker@adacore.com
Subject: Re: [patch] i386-nto-tdep.c: Add support for xmm registers.
Date: Thu, 11 Jun 2009 19:59:00 -0000	[thread overview]
Message-ID: <200906111958.n5BJwSua020394@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <4A312369.900@qnx.com> (message from Aleksandar Ristovski on Thu, 	11 Jun 2009 11:31:53 -0400)

> From: Aleksandar Ristovski <aristovski@qnx.com>
> Date:  Thu, 11 Jun 2009 11:31:53 -0400
> 
> Thank you for reviewing the patch!
> 
> Joel Brobecker wrote:
> >> Add support for XMM registers.
> >> * i386-nto-tdep.c (i386_nto_target): Remove definition.
> >> (i386nto_regset_id): Add case for SSE register set.
> >> (i386nto_register_area): Correctly calculate offsets and sizes for all 
> >> supported registers.
> >> (I386_NTO_SIGCONTEXT_OFFSET): Remove macro definition.
> >> (i386nto_sigcontext_addr): Use better method of retrieving sigcontext 
> >> pointer.
> >> (init_i386nto_ops): Remove i386_nto_target.
> >> (i386nto_init_abi): Remove nto_svr4_so_ops indirection. Properly setup 
> >> tdep params sc_reg_offset and sc_num_regs. Remove nto_svr4_so_ops and 
> >> make changes accordingly.
> > 
> > I won't pretend I understand everything you do in this patch, but
> > the pieces that are related to registers and sigcontext seem to be
> > sensible.
> > 
> > However, I found a few hunks which I think are not related to XMM
> > register support, but rather to shared library support...
> 
> Attached is "clean" XMM support patch.
> 
> Thanks,
> 
> -- 
> Aleksandar Ristovski
> QNX Software Systems
> 
> ChangeLog:
> 
> 
> 	Add support for XMM registers.
> 	* i386-nto-tdep.c (i386nto_regset_id): Add case for SSE 
> register set.
> 	(i386nto_register_area): Correctly calculate offsets and 
> sizes for
> 	all supported registers.

Looks reasonable to me (assuming the wrapped lines in the ChangeLog
are caused by your broken mail client).


  parent reply	other threads:[~2009-06-11 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 19:20 Aleksandar Ristovski
2009-06-09  2:23 ` Aleksandar Ristovski
2009-06-11 15:09 ` Joel Brobecker
2009-06-11 15:32   ` Aleksandar Ristovski
2009-06-11 15:37     ` Joel Brobecker
2009-06-11 17:13       ` Aleksandar Ristovski
2009-06-11 19:59     ` Mark Kettenis [this message]
2009-06-11 20:03       ` Aleksandar Ristovski

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=200906111958.n5BJwSua020394@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=aristovski@qnx.com \
    --cc=brobecker@adacore.com \
    --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