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 5/11] Add M32R_MAX_REGISTER_SIZE
Date: Wed, 12 Apr 2017 08:22:00 -0000	[thread overview]
Message-ID: <12D8FEDF-F829-4AF0-93B4-461213904B4B@arm.com> (raw)
In-Reply-To: <86inmbwc3v.fsf@gmail.com>


> On 11 Apr 2017, at 10:02, Yao Qi <qiyaoltc@gmail.com> wrote:
> 
> Alan Hayward <Alan.Hayward@arm.com> writes:
> 
>> +/* Big enough to hold the size of the largest register in bytes.  */
>> +#define M32R_MAX_REGISTER_SIZE	4
>> +
>> #endif /* m32r-tdep.h */
>> diff --git a/gdb/m32r-tdep.c b/gdb/m32r-tdep.c
>> index 40f29d343b91f254cce2dd783553795c9c990eff..cb53a352b2d47068ad7cd5dacd3325d66bd77964 100644
>> --- a/gdb/m32r-tdep.c
>> +++ b/gdb/m32r-tdep.c
>> @@ -677,7 +677,7 @@ m32r_push_dummy_call (struct gdbarch *gdbarch, struct value *function,
>>   enum type_code typecode;
>>   CORE_ADDR regval;
>>   gdb_byte *val;
>> -  gdb_byte valbuf[MAX_REGISTER_SIZE];
>> +  gdb_byte valbuf[M32R_MAX_REGISTER_SIZE];
> 
> valbuf is only used for argument registers, r0 - r3.  Can you rename
> M32R_MAX_REGISTER_SIZE with M32R_ARG_REGISTER_SIZE? and move its
> definition into m32r-tdep.c.
> 
> /* The size of argument registers (r0 - r3) in bytes.  */
> #define M32R_ARG_REGISTER_SIZE 4
> 
> OK with the change.
> 
> -- 
> Yao (齐尧)

Ok, pushed the following patch:

Alan.


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

	* m32r-tdep.c M32R_ARG_REGISTER_SIZE: Added.
	(m32r_push_dummy_call): Use M32R_ARG_REGISTER_SIZE.

diff --git a/gdb/m32r-tdep.c b/gdb/m32r-tdep.c
index 1d0d7ed..4701f7a 100644
--- a/gdb/m32r-tdep.c
+++ b/gdb/m32r-tdep.c
@@ -39,6 +39,9 @@
#include "m32r-tdep.h"
#include <algorithm>

+/* The size of the argument registers (r0 - r3) in bytes.  */
+#define M32R_ARG_REGISTER_SIZE 4
+
/* Local functions */

extern void _initialize_m32r_tdep (void);
@@ -677,7 +680,7 @@ m32r_push_dummy_call (struct gdbarch *gdbarch, struct value *function,
  enum type_code typecode;
  CORE_ADDR regval;
  gdb_byte *val;
-  gdb_byte valbuf[MAX_REGISTER_SIZE];
+  gdb_byte valbuf[M32R_ARG_REGISTER_SIZE];
  int len;

  /* First force sp to a 4-byte alignment.  */



  reply	other threads:[~2017-04-12  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 10:13 Alan Hayward
2017-04-11  9:02 ` Yao Qi
2017-04-12  8:22   ` Alan Hayward [this message]
     [not found]     ` <CAH=s-PP8Pkk7FO6C2EGaBGg8_gLyY8VHJxSfie3rYBx38_ac2g@mail.gmail.com>
2017-04-12  8:54       ` Alan Hayward

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=12D8FEDF-F829-4AF0-93B4-461213904B4B@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