public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Yvan Roux <yvan.roux@foss.st.com>, gdb-patches@sourceware.org
Cc: Torbjorn SVENSSON <torbjorn.svensson@st.com>
Subject: Re: [PATCH] gdb/arm: Cleanup: use hex for offsets
Date: Thu, 26 May 2022 08:29:38 +0100	[thread overview]
Message-ID: <c2f7c93e-1790-795e-af89-7919b3116a61@arm.com> (raw)
In-Reply-To: <20220525151240.GA11828@gnbcxd0114.gnb.st.com>

On 5/25/22 16:12, Yvan Roux wrote:
> Hi,
> 
> Changed offset from decimal to hex to match architecture reference
> manual terminology and keep coherency with the rest of the code.
> 
> Signed-off-by: Torbj�rn SVENSSON <torbjorn.svensson@st.com>
> Signed-off-by: Yvan Roux <yvan.roux@foss.st.com>
> ---
>   gdb/arm-tdep.c | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
> index 49664093f00..21cd80c5fcc 100644
> --- a/gdb/arm-tdep.c
> +++ b/gdb/arm-tdep.c
> @@ -3438,13 +3438,13 @@ arm_m_exception_cache (struct frame_info *this_frame)
>        "B1.5.6 Exception entry behavior" in
>        "ARMv7-M Architecture Reference Manual".  */
>     cache->saved_regs[0].set_addr (unwound_sp + sp_r0_offset);
> -  cache->saved_regs[1].set_addr (unwound_sp + sp_r0_offset + 4);
> -  cache->saved_regs[2].set_addr (unwound_sp + sp_r0_offset + 8);
> -  cache->saved_regs[3].set_addr (unwound_sp + sp_r0_offset + 12);
> -  cache->saved_regs[ARM_IP_REGNUM].set_addr (unwound_sp + sp_r0_offset + 16);
> -  cache->saved_regs[ARM_LR_REGNUM].set_addr (unwound_sp + sp_r0_offset + 20);
> -  cache->saved_regs[ARM_PC_REGNUM].set_addr (unwound_sp + sp_r0_offset + 24);
> -  cache->saved_regs[ARM_PS_REGNUM].set_addr (unwound_sp + sp_r0_offset + 28);
> +  cache->saved_regs[1].set_addr (unwound_sp + sp_r0_offset + 0x04);
> +  cache->saved_regs[2].set_addr (unwound_sp + sp_r0_offset + 0x08);
> +  cache->saved_regs[3].set_addr (unwound_sp + sp_r0_offset + 0x0C);
> +  cache->saved_regs[ARM_IP_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x10);
> +  cache->saved_regs[ARM_LR_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x14);
> +  cache->saved_regs[ARM_PC_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x18);
> +  cache->saved_regs[ARM_PS_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x1C);
>   
>     /* Check EXC_RETURN bit FTYPE if extended stack frame (FPU regs stored)
>        type used.  */
> @@ -3499,7 +3499,7 @@ arm_m_exception_cache (struct frame_info *this_frame)
>     /* If bit 9 of the saved xPSR is set, then there is a four-byte
>        aligner between the top of the 32-byte stack frame and the
>        previous context's stack pointer.  */
> -  if (safe_read_memory_integer (unwound_sp + sp_r0_offset + 28, 4, byte_order, &xpsr)
> +  if (safe_read_memory_integer (unwound_sp + sp_r0_offset + 0x1C, 4, byte_order, &xpsr)
>         && (xpsr & (1 << 9)) != 0)
>       arm_cache_set_active_sp_value (cache, tdep,
>   				   arm_cache_get_prev_sp_value (cache, tdep) + 4);

Thanks. This is OK with the long lines fixed. The last one is going over the limit of 80 cols.

  reply	other threads:[~2022-05-26  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 15:12 Yvan Roux
2022-05-26  7:29 ` Luis Machado [this message]
2022-05-31 13:23   ` Yvan Roux

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=c2f7c93e-1790-795e-af89-7919b3116a61@arm.com \
    --to=luis.machado@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=torbjorn.svensson@st.com \
    --cc=yvan.roux@foss.st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).