Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H.J. Lu" <hongjiu.lu@intel.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: PATCH: Also check for `movl %esp, %ebp' for x32
Date: Tue, 17 Apr 2012 11:35:00 -0000	[thread overview]
Message-ID: <4F8D4AC8.6010402@codesourcery.com> (raw)
In-Reply-To: <20120410202953.GA23862@intel.com>

On 04/11/2012 04:29 AM, H.J. Lu wrote:
> -	  && memcmp (buf, mov_rsp_rbp_2, 3) != 0)
> +	  && memcmp (buf, mov_rsp_rbp_2, 3) != 0
> +	  && (gdbarch_ptr_bit (gdbarch) == 64
> +	      || (memcmp (buf, mov_rsp_rbp_1 + 1, 2) != 0
                                                  ^^
> +		  && memcmp (buf, mov_rsp_rbp_2 + 1, 2) != 0)))
                                                     ^^

I don't understand these two constants "2" here.  Does this mean the
encoding of `movl %esp, %ebp' is { 0x48, 0x89 } and { 0x48, 0x8b }?  If
my understand is correct, why don't we define two new array
"movl_esp_ebp_1" and "movl_esp_ebp_2"? which is easier to read/understand.

-- 
Yao (齐尧)


  parent reply	other threads:[~2012-04-17 10:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 20:52 H.J. Lu
2012-04-16 17:54 ` PING: " H.J. Lu
2012-04-17 11:35 ` Yao Qi [this message]
2012-04-17 14:41   ` H.J. Lu
2012-04-17 11:51 ` Mark Kettenis
2012-04-17 14:32   ` H.J. Lu
2012-04-24 16:33     ` H.J. Lu
2012-04-29 23:21       ` H.J. Lu
2012-05-02 21:44         ` Mark Kettenis
2012-05-02 22:14           ` H.J. Lu
2012-05-03 19:01             ` H.J. Lu
2012-05-03 21:50               ` Mark Kettenis
2012-05-03 21:52                 ` H.J. Lu
2012-05-06 20:31                 ` Mark Kettenis
2012-05-06 20:42                   ` H.J. Lu

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=4F8D4AC8.6010402@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=hongjiu.lu@intel.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