Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Victor Collod <vcollod@nvidia.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] Refactor amd64_analyze_prologue
Date: Sun, 21 Jun 2020 07:38:42 -0400	[thread overview]
Message-ID: <0cc93067-1313-6434-4330-61a21736376f@simark.ca> (raw)
In-Reply-To: <20200611225455.9354-3-vcollod@nvidia.com>

On 2020-06-11 6:54 p.m., Victor Collod via Gdb-patches wrote:
> * merge op and the buf array, which were both used for storing code
> * invert conditions to avoid long nested ifs
> * use target_read_code instead of read_code to gracefully handle errors
> * `if (current_pc <= pc)' felt backwards, as current_pc doesn't change,
>   and the test could be described as "stop if pc went past current_pc"

I'd appreciate if you could do one patch per change here.  They'd each be
more trivial to review and ensure they are ok.

> 2020-06-11  Victor Collod  <vcollod@nvidia.com>
> 
> 	* amd64-tdep.c (amd64_analyze_prologue): Make the function more readable.
> ---
>  gdb/amd64-tdep.c | 93 ++++++++++++++++++++++++++----------------------
>  1 file changed, 50 insertions(+), 43 deletions(-)
> 
> diff --git a/gdb/amd64-tdep.c b/gdb/amd64-tdep.c
> index 0ce9fbc2997..6c1a4a138de 100644
> --- a/gdb/amd64-tdep.c
> +++ b/gdb/amd64-tdep.c
> @@ -2374,7 +2374,6 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
>  			CORE_ADDR pc, CORE_ADDR current_pc,
>  			struct amd64_frame_cache *cache)
>  {
> -  enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
>    /* The `endbr64` instruction.  */
>    static const gdb_byte endbr64[4] = { 0xf3, 0x0f, 0x1e, 0xfa };
>    /* There are two variations of movq %rsp, %rbp.  */
> @@ -2384,10 +2383,10 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
>    static const gdb_byte mov_esp_ebp_1[2] = { 0x89, 0xe5 };
>    static const gdb_byte mov_esp_ebp_2[2] = { 0x8b, 0xec };
>  
> -  gdb_byte buf[3];
> -  gdb_byte op;
> +  gdb_byte buf[4];
>  
> -  if (current_pc <= pc)
> +  /* Analysis must not go past current_pc */

Take the habit of starting each comment with a capital letter, finishing with a period and two
spaces (unless it's not really a sentence, like `/* no-op */`).

> +  if (pc >= current_pc)
>      return current_pc;
>  
>    if (gdbarch_ptr_bit (gdbarch) == 32)
> @@ -2395,57 +2394,65 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
>    else
>      pc = amd64_analyze_stack_align (pc, current_pc, cache);
>  
> -  op = read_code_unsigned_integer (pc, 1, byte_order);
> -
> -  /* Check for the `endbr64` instruction, skip it if found.  */
> -  if (op == endbr64[0])
> +  /* Try to read enough bytes to check for `endbr64'  */
> +  if (target_read_code (pc, buf, 4) != 0)
> +    {
> +      /* If it fails, read just enough data for `pushq %rbp' */
> +      if (target_read_code (pc, buf, 1) != 0)
> +	return pc;
> +    }
> +  /* If reading succeeded, check for the `endbr64' instruction and skip it if found.  */
> +  else if (memcmp (buf, endbr64, sizeof (endbr64)) == 0)
>      {
> -      read_code (pc + 1, buf, 3);
> +      pc += sizeof (endbr64);
> +      /* If we went past the allowed bound, stop */
> +      if (pc >= current_pc)
> +	return current_pc;

For readability, please add an empty line after return statements, when there
is another statement after it.

Thanks,

Simon


  reply	other threads:[~2020-06-21 11:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 23:23 [PATCH] Improve intel IBT support Victor Collod
2020-06-05 23:55 ` Victor Collod
2020-06-11  3:18 ` Simon Marchi
2020-06-11 22:54   ` [PATCH v2 0/2] " Victor Collod
2020-06-11 22:54     ` [PATCH v2 1/2] Add i386 support for endbr skipping Victor Collod
2020-06-21 11:27       ` Simon Marchi
2020-06-11 22:54     ` [PATCH v2 2/2] Refactor amd64_analyze_prologue Victor Collod
2020-06-21 11:38       ` Simon Marchi [this message]
2020-06-24  1:28         ` [PATCH v3 0/7] Improve intel IBT support Victor Collod
2020-06-24  1:28           ` [PATCH v3 1/7] Add i386 support for endbr skipping Victor Collod
2020-08-06 13:57             ` Simon Marchi
2020-09-19  0:29               ` [PATCH] gdb: Update i386_analyze_prologue to skip endbr32 H.J. Lu
2020-09-19  0:38                 ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 2/7] amd64_analyze_prologue: swap upper bound check condition operands Victor Collod
2020-08-06 14:41             ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 3/7] amd64_analyze_prologue: merge op and buf Victor Collod
2020-08-06 14:55             ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 4/7] amd64_analyze_prologue: invert a condition for readability Victor Collod
2020-08-06 14:57             ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 5/7] amd64_analyze_prologue: gradually update pc Victor Collod
2020-08-06 14:59             ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 6/7] amd64_analyze_prologue: fix incorrect comment Victor Collod
2020-08-06 15:05             ` Simon Marchi
2020-06-24  1:28           ` [PATCH v3 7/7] amd64_analyze_prologue: use target_read_code instead of read_code Victor Collod
2020-08-06 15:01             ` Simon Marchi
2020-08-05 21:44           ` [PATCH v3 0/7] Improve intel IBT support Victor Collod

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=0cc93067-1313-6434-4330-61a21736376f@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=vcollod@nvidia.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