Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH 7/11] Add BFIN_MAX_REGISTER_SIZE
Date: Fri, 07 Apr 2017 08:32:00 -0000	[thread overview]
Message-ID: <E588701B-CEBD-44E3-9664-5535862786A2@arm.com> (raw)
In-Reply-To: <86d1croshn.fsf@gmail.com>


> On 5 Apr 2017, at 15:10, Yao Qi <qiyaoltc@gmail.com> wrote:
> 
> Alan Hayward <Alan.Hayward@arm.com> writes:
> 
>> Is it not clearer code to add and use a macro rather than a magic number ?
>> 
> 
> Macro is better, but "buf[4]" is not that magic, because it is only used
> within bfin_pseudo_register_read, or we can define ASTAT_REGISTER_SIZE.
> 
>> It’s also not obvious anywhere that the astat register is 32bits. I had to go
>> digging inside regformats/reg-bfin.dat before I found it out.
> 
> It is easier to figure out the size of a specific register than the max
> size of a set of registers.
> 
>> 
>> Given that BFIN_MAX_REGISTER_SIZE is also 4, it compiles to the same
>> size anyway.
> 
> "gdb_byte buf[BFIN_MAX_REGISTER_SIZE]" is fine to me.  Could you define
> BFIN_MAX_REGISTER_SIZE in bfin-tdep.c instead of .h?  It is not used
> elsewhere.
> 

Ok, pushed the following:

2017-04-07  Alan Hayward  <alan.hayward@arm.com>

	* bfin-tdep.c (BFIN_MAX_REGISTER_SIZE): Add.
	(bfin_pseudo_register_read): Use BFIN_MAX_REGISTER_SIZE.
	(bfin_pseudo_register_write): Likewise


diff --git a/gdb/bfin-tdep.c b/gdb/bfin-tdep.c
index 3df1ba387a323dc6827b1189432f8877d1833184..c590a9132c00f539b5c6e57b8f156845ff50acad 100644
--- a/gdb/bfin-tdep.c
+++ b/gdb/bfin-tdep.c
@@ -241,6 +241,8 @@ static const int map_gcc_gdb[] =
   BFIN_LB1_REGNUM
 };

+/* Big enough to hold the size of the largest register in bytes.  */
+#define BFIN_MAX_REGISTER_SIZE	4

 struct bfin_frame_cache
 {
@@ -689,7 +691,7 @@ static enum register_status
 bfin_pseudo_register_read (struct gdbarch *gdbarch, struct regcache *regcache,
 			   int regnum, gdb_byte *buffer)
 {
-  gdb_byte *buf = (gdb_byte *) alloca (MAX_REGISTER_SIZE);
+  gdb_byte buf[BFIN_MAX_REGISTER_SIZE];
   enum register_status status;

   if (regnum != BFIN_CC_REGNUM)
@@ -710,7 +712,7 @@ static void
 bfin_pseudo_register_write (struct gdbarch *gdbarch, struct regcache *regcache,
 			    int regnum, const gdb_byte *buffer)
 {
-  gdb_byte *buf = (gdb_byte *) alloca (MAX_REGISTER_SIZE);
+  gdb_byte buf[BFIN_MAX_REGISTER_SIZE];

   if (regnum != BFIN_CC_REGNUM)
     internal_error (__FILE__, __LINE__,



  parent reply	other threads:[~2017-04-07  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 10:14 Alan Hayward
     [not found] ` <86tw63p2rx.fsf@gmail.com>
     [not found]   ` <EDE97F7B-EFCE-4B4D-B996-C458F1DC7E56@arm.com>
2017-04-05 13:50     ` Andreas Schwab
2017-04-05 13:57       ` Alan Hayward
     [not found]     ` <86d1croshn.fsf@gmail.com>
2017-04-07  8:32       ` Alan Hayward [this message]
     [not found] ` <3239de71-1e7c-22dd-172d-56a3baad292b@redhat.com>
2017-04-05 15:51   ` Alan Hayward
2017-04-07 16:04     ` Yao Qi
2017-04-07 16:22       ` Alan Hayward
2017-04-14 17:26 ` Mike Frysinger

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=E588701B-CEBD-44E3-9664-5535862786A2@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=qiyaoltc@gmail.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