From: Alan Hayward <Alan.Hayward@arm.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Remove MAX_REGISTER_SIZE from mi/mi-main.c
Date: Thu, 08 Jun 2017 12:57:00 -0000 [thread overview]
Message-ID: <B92EB568-29C2-4CD8-B3BF-3F3F552366EE@arm.com> (raw)
In-Reply-To: <0fd04925-3200-53b9-5a7d-904ea028c3b0@redhat.com>
> On 8 Jun 2017, at 10:55, Pedro Alves <palves@redhat.com> wrote:
>
> On 06/08/2017 10:42 AM, Alan Hayward wrote:
>
>> /* Get register contents and compare. */
>> - prev_status = regcache_cooked_read (prev_regs, regnum, prev_buffer);
>> - this_status = regcache_cooked_read (this_regs, regnum, this_buffer);
>> -
>> - if (this_status != prev_status)
>> - return 1;
>> - else if (this_status == REG_VALID)
>> - return memcmp (prev_buffer, this_buffer,
>> - register_size (gdbarch, regnum)) != 0;
>> + prev_value = prev_regs->cooked_read_value (regnum);
>> + this_value = this_regs->cooked_read_value (regnum);
>> + gdb_assert (prev_value != NULL);
>> + gdb_assert (this_value != NULL);
>> +
>> + if (value_optimized_out (prev_value) != value_optimized_out (this_value)
>> + || value_entirely_available (prev_value)
>> + != value_entirely_available (this_value))
>> + ret = 1;
>> + if (value_optimized_out (prev_value)
>> + || !value_entirely_available (prev_value))
>> + ret = 0;
>> else
>> - return 0;
>> + ret = memcmp (value_contents_all (prev_value),
>> + value_contents_all (this_value),
>> + register_size (gdbarch, regnum)) != 0;
>> +
>> + release_value (prev_value);
>> + release_value (this_value);
>> + value_free (prev_value);
>> + value_free (this_value);
>> + return ret;
>> }
>>
>
> Use value_contents_eq?
That simplifies things!
Updated using value_contents_eq.
Tested on a --enable-targets=all build
No regressions in gdb.mi/*.exp
Also tested with board files unix and native-gdbserver.
Ok to commit?
Alan.
2017-06-08 Alan Hayward <alan.hayward@arm.com>
* mi/mi-main.c (register_changed_p): Use cooked_read_value
diff --git a/gdb/mi/mi-main.c b/gdb/mi/mi-main.c
index bdc5dda30537c7e5797fb8c44b689a63c5c0f4b8..9cbd3a454d20b4429725a00328840e4b4cce47f9 100644
--- a/gdb/mi/mi-main.c
+++ b/gdb/mi/mi-main.c
@@ -1111,10 +1111,8 @@ register_changed_p (int regnum, struct regcache *prev_regs,
struct regcache *this_regs)
{
struct gdbarch *gdbarch = get_regcache_arch (this_regs);
- gdb_byte prev_buffer[MAX_REGISTER_SIZE];
- gdb_byte this_buffer[MAX_REGISTER_SIZE];
- enum register_status prev_status;
- enum register_status this_status;
+ struct value *prev_value, *this_value;
+ int ret;
/* First time through or after gdbarch change consider all registers
as changed. */
@@ -1122,16 +1120,17 @@ register_changed_p (int regnum, struct regcache *prev_regs,
return 1;
/* Get register contents and compare. */
- prev_status = regcache_cooked_read (prev_regs, regnum, prev_buffer);
- this_status = regcache_cooked_read (this_regs, regnum, this_buffer);
+ prev_value = prev_regs->cooked_read_value (regnum);
+ this_value = this_regs->cooked_read_value (regnum);
- if (this_status != prev_status)
- return 1;
- else if (this_status == REG_VALID)
- return memcmp (prev_buffer, this_buffer,
- register_size (gdbarch, regnum)) != 0;
- else
- return 0;
+ ret = value_contents_eq (prev_value, 0, this_value, 0,
+ register_size (gdbarch, regnum)) == 0;
+
+ release_value (prev_value);
+ release_value (this_value);
+ value_free (prev_value);
+ value_free (this_value);
+ return ret;
}
/* Return a list of register number and value pairs. The valid
next prev parent reply other threads:[~2017-06-08 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA96E9D-7905-4D03-9424-2BC71D117CE2@arm.com>
2017-06-08 9:55 ` Pedro Alves
2017-06-08 12:57 ` Alan Hayward [this message]
2017-06-08 13:00 ` Pedro Alves
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=B92EB568-29C2-4CD8-B3BF-3F3F552366EE@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=palves@redhat.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