Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Simon Cook <simon.cook@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/riscv: Improve flen length determiniation
Date: Wed, 22 May 2019 12:05:00 -0000	[thread overview]
Message-ID: <20190522120525.GI2568@embecosm.com> (raw)
In-Reply-To: <20190522113745.26750-1-simon.cook@embecosm.com>

* Simon Cook <simon.cook@embecosm.com> [2019-05-22 12:37:45 +0100]:

> This solves an assertion failure when a remote provides a target
> description which only refers to floating point registers by their
> hardware name (e.g. f0), rather than their ABI name (e.g. ft0). GDB
> assumed that should the floating point register feature be presented,
> it would contain a register called ft0.
> 
> The floating point length is now instead determined by searching for
> the same register, but looking for any of its aliases.
> 
> gdb/ChangeLog:
> 
> 	* riscv-tdep.c (riscv_gdbarch_init): Support determining flen from
> 	target descriptions using exclusively floating point register name
> 	aliases.

Thanks for looking at this.

I've pushed your patch to master.

Thanks,
Andrew


> ---
>  gdb/ChangeLog    |  6 ++++++
>  gdb/riscv-tdep.c | 17 ++++++++++++++++-
>  2 files changed, 22 insertions(+), 1 deletion(-)
> 
> diff --git a/gdb/riscv-tdep.c b/gdb/riscv-tdep.c
> index 4fe07ef437..072c8e3720 100644
> --- a/gdb/riscv-tdep.c
> +++ b/gdb/riscv-tdep.c
> @@ -3094,7 +3094,22 @@ riscv_gdbarch_init (struct gdbarch_info info,
>        valid_p &= riscv_check_tdesc_feature (tdesc_data, feature_fpu,
>                                              &riscv_freg_feature);
>  
> -      int bitsize = tdesc_register_bitsize (feature_fpu, "ft0");
> +      /* Search for the first floating point register (by any alias), to
> +         determine the bitsize.  */
> +      int bitsize = -1;
> +      const auto &fp0 = riscv_freg_feature.registers[0];
> +
> +      for (const char *name : fp0.names)
> +	{
> +	  if (tdesc_unnumbered_register (feature_fpu, name))
> +	    {
> +	      bitsize = tdesc_register_bitsize (feature_fpu, name);
> +	      break;
> +	    }
> +	}
> +
> +      gdb_assert (bitsize != -1);
> +
>        features.flen = (bitsize / 8);
>  
>        if (riscv_debug_gdbarch)
> -- 
> 2.17.1
> 


      reply	other threads:[~2019-05-22 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 11:37 Simon Cook
2019-05-22 12:05 ` Andrew Burgess [this message]

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=20190522120525.GI2568@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.cook@embecosm.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