Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Jiang Jilin <freephp@gmail.com>, burlen <burlen.loring@gmail.com>,
	 	"gdb@sourceware.org" <gdb@sourceware.org>,
	Michael Snyder <msnyder@vmware.com>
Subject: Re: reverse execution
Date: Mon, 19 Oct 2009 08:04:00 -0000	[thread overview]
Message-ID: <daef60380910182358o1380052eh377142c774381c22@mail.gmail.com> (raw)
In-Reply-To: <4ADA91C4.7010106@vmware.com>

Hi Oza,

are you working on or done with sse insn?

Thanks,
Hui

On Sun, Oct 18, 2009 at 11:55, Michael Snyder <msnyder@vmware.com> wrote:
> Jiang Jilin wrote:
>>
>> On Sun, Oct 18, 2009 at 10:45 AM, Hui Zhu <teawater@gmail.com> wrote:
>>>
>>> Thanks Jilin,
>>>
>>> Sorry I made a mistake when we told about it.  I want to say 0xf10
>>> series insn (they seems called sse insn), but I said mmx insn.
>>
>> Aha, I misunderstood what you said. I take a glance at the specific and
>> find they are relevant with mmx, so you are right. :)
>>
>>> These 0xf10 insn seems control the xmm reg, you can see the values of
>>> these reg whith gdb cmd "info info all-registers".
>>
>> Yeah, It seems I cannot delay the work for mmx insn. :)
>
> Don't forget that Paawan Oza has already said he was going to
> work on the reverse MMX support.  Wouldn't want to see you two
> guys duplicating effort...
>
>


  reply	other threads:[~2009-10-19  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 21:07 burlen
2009-10-16 21:55 ` Michael Snyder
2009-10-17 23:49   ` Daniel Jacobowitz
2009-10-18  2:19 ` Jiang Jilin
2009-10-18  3:18   ` Hui Zhu
2009-10-18  4:01     ` Jiang Jilin
2009-10-18 11:18       ` Michael Snyder
2009-10-19  8:04         ` Hui Zhu [this message]
2013-04-08 14:37 ishare
2013-04-08 14:47 ` Jan Kratochvil

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=daef60380910182358o1380052eh377142c774381c22@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=burlen.loring@gmail.com \
    --cc=freephp@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=paawan1982@yahoo.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