Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb-patches@sourceware.org, Alan.Hayward@arm.com
Subject: Re: [PATCH] [AArch64] Fix erroneous use of spu architecture bfd
Date: Sun, 05 Jan 2020 06:27:00 -0000	[thread overview]
Message-ID: <20200105062746.GC12588@adacore.com> (raw)
In-Reply-To: <20200103191512.28770-1-luis.machado@linaro.org>

Hi Luis,

> While investigating some SVE code, i noticed the use of two spu bfd variables.
> 
> This looks like an oversight, as the "id" field is available for non-spu
> architectures as well, even though its primary use was the Cell BE
> architecture.
> 
> The following patch fixes this.
> 
> gdb/ChangeLog:
> 
> 2020-01-03  Luis Machado  <luis.machado@linaro.org>
> 
> 	* aarch64-linux-nat.c
> 	(aarch64_linux_nat_target::thread_architecture): Use bfd_arch_aarch64
> 	and bfd_mach_aarch64.
> 
> Change-Id: I817673e9a12cadfa88638870f0ff524241cf6a34


I think the patch looks pretty clear to me ;-), so you can go ahead
and push.

Or perhaps, before doing so: Since the Gerrit experiment is being
put on hold, you might want to remove your commit hook, and then
remove the "Change-Id" field above...

Thanks for the patch!

> ---
>  gdb/aarch64-linux-nat.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/aarch64-linux-nat.c b/gdb/aarch64-linux-nat.c
> index 62f5cdb1fc..4e712ebfb7 100644
> --- a/gdb/aarch64-linux-nat.c
> +++ b/gdb/aarch64-linux-nat.c
> @@ -970,7 +970,7 @@ aarch64_linux_nat_target::thread_architecture (ptid_t ptid)
>       unavailable, to distinguish from an unset value of 0.  */
>    struct gdbarch_info info;
>    gdbarch_info_init (&info);
> -  info.bfd_arch_info = bfd_lookup_arch (bfd_arch_spu, bfd_mach_spu);
> +  info.bfd_arch_info = bfd_lookup_arch (bfd_arch_aarch64, bfd_mach_aarch64);
>    info.id = (int *) (vq == 0 ? -1 : vq);
>    return gdbarch_find_by_info (info);
>  }
> -- 
> 2.17.1

-- 
Joel


  reply	other threads:[~2020-01-05  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 19:15 Luis Machado
2020-01-05  6:27 ` Joel Brobecker [this message]
2020-01-05 12:00   ` Luis Machado

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=20200105062746.GC12588@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.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