Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
	gdb ml <gdb@sourceware.org>,
	  Pedro Alves <pedro@codesourcery.com>,
	  Marc Khouzam <marc.khouzam@ericsson.com>,
	  Michael Snyder <msnyder@vmware.com>,
	Eli Zaretskii <eliz@gnu.org>,
	  Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: MMX and floating point insn suport for reversible debugging
Date: Sat, 09 May 2009 14:45:00 -0000	[thread overview]
Message-ID: <866937.71751.qm@web36208.mail.mud.yahoo.com> (raw)


Hi,

yes.
I guess, MMX support needs to be added here, 

case 0x0f06:
       break;
       /* MMX/SSE/SSE2/PNI support */
       /* XXX */ 

but before I would start adding floating point support.

I have 2 doubts:
-> in function record_arch_list_add_reg
we are doing:
rec->u.reg.val = (gdb_byte *) xmalloc (MAX_REGISTER_SIZE);
we are allocating 128 bytes.....
but I suppose only SSE extensions can fully utilize the memory...
for rest of the registers, are not we allocating more memory than required for record ?

-> SSE support is not there in linux krenel (ptrace), I also read in some piece of comments also.
but SSE support (PT_GETXMMREGS) is suported in openbsd.

with that sense do we need to add SSE/SSE2/SSE3/SSE4 
support in i386-tdep.c generically ?  (of coursse our first priority is to add floating point suport, but I am querying out of my curiousity)

Regards,
Oza.


--- On Thu, 5/7/09, Hui Zhu <teawater@gmail.com> wrote:

> From: Hui Zhu <teawater@gmail.com>
> Subject: Re: MMX and floating point insn suport for reversible debugging
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: "Thiago Jung Bauermann" <bauerman@br.ibm.com>, "gdb ml" <gdb@sourceware.org>, "Pedro Alves" <pedro@codesourcery.com>, "Marc Khouzam" <marc.khouzam@ericsson.com>, "Michael Snyder" <msnyder@vmware.com>, "Eli Zaretskii" <eliz@gnu.org>, "Mark Kettenis" <mark.kettenis@xs4all.nl>
> Date: Thursday, May 7, 2009, 8:24 AM
> On Thu, May 7, 2009 at 02:02, paawan
> oza <paawan1982@yahoo.com>
> wrote:
> >
> > Hi Hui,
> >
> > I have started understanding and working on point-1.
> > I have some questions. please let me know my
> understanding is correct ?
> >
> > 1) i386-tdep.c is the one which has been done for
> record-replay. which basically takes care of disassembling
> insns...
> > but I see some code regarding MMX and x87FPU already
> available.
> > may I know exactly, what support is missing ?
> >
> 
>     case 0x0f06:
>       break;
> 
>       /* MMX/SSE/SSE2/PNI support */
>       /* XXX */
> 
>     default:
> 
> Your mean is this part?
> 
> 
> And I suggest you can begin with float point insn
> first.  It doesn't
> record float point reg change.
> 
> 
> Thanks,
> Hui
> 




             reply	other threads:[~2009-05-09 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 14:45 paawan oza [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-10 13:45 paawan oza
2009-05-10  6:40 paawan oza
2009-05-10  6:37 paawan oza
2009-05-10  8:39 ` Mark Kettenis
2009-05-06 18:02 paawan oza
2009-05-07  2:54 ` Hui Zhu

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=866937.71751.qm@web36208.mail.mud.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=bauerman@br.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=teawater@gmail.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