Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Rewrite the codes for opcode 0x0f01 and add more instructions support
Date: Tue, 29 Mar 2011 12:21:00 -0000	[thread overview]
Message-ID: <4D91BE41.2010107@codesourcery.com> (raw)
In-Reply-To: <AANLkTinrdVcu-5YpHZ+By99OcowB5fU1W7rs524PohoJ@mail.gmail.com>

On 03/29/2011 06:11 PM, Jiang Jilin wrote:

I am not the people to approve this patch.  Some comments on code format
and indent.

> 2011-03-29  Jiang Jilin  <freephp@gmail.com>

There should be a newline here.  Please reference other changelog entries.
>       * i386-tdep.c (i386_process_record): Rewrite the codes for
>       opcode 0x0f01 and add more instructions support

> +         switch (reg_rm)
> +           {
> +              /* vmcall */
> +              case 0x01:
> +                /* vmlaunch */
Looks like there are two extra spaces in front of your comment.  Please
remove them.  There are several instances of this problem in your patch.

> +
> +                    /* We have to store at least (4 + 2 = 6) bytes,
> +                       or (8 + 2 = 10) bytes at most.  */

According to my limited English knowledge, it should be "6 bytes at
least *and* 10 bytes at most".

> +                    if (i386_record_lea_modrm_addr (&ir, &tmpu64))
> +                      return -1;


-- 
Yao (齐尧)


  reply	other threads:[~2011-03-29 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 13:46 Jiang Jilin
2009-10-12  2:08 ` Michael Snyder
2009-10-12  2:21   ` Jiang Jilin
2010-09-16 18:01     ` Jiang Jilin
2010-09-17  8:33       ` Michael Snyder
2011-03-29 12:07         ` Jiang Jilin
2011-03-29 12:21           ` Yao Qi [this message]
2011-03-29 14:28             ` Jiang Jilin
2011-05-19 19:27               ` Tom Tromey

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=4D91BE41.2010107@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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