From: Yufeng Zhang <Yufeng.Zhang@arm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: unnecessary aarch64_write_pc ?
Date: Wed, 17 Apr 2013 17:07:00 -0000 [thread overview]
Message-ID: <516EB29D.2030409@arm.com> (raw)
In-Reply-To: <20130415125021.GB3525@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Hello Joel,
On 04/15/13 13:50, Joel Brobecker wrote:
> I noticed the following code:
>
>> /* Implement the "write_pc" gdbarch method. */
>>
>> static void
>> aarch64_write_pc (struct regcache *regcache, CORE_ADDR pc)
>> {
>> regcache_cooked_write_unsigned (regcache, AARCH64_PC_REGNUM, pc);
>> }
>
> But looking at the only use of the gdbarch_write_pc function, I see:
>
>> void
>> regcache_write_pc (struct regcache *regcache, CORE_ADDR pc)
>> {
>> struct gdbarch *gdbarch = get_regcache_arch (regcache);
>>
>> if (gdbarch_write_pc_p (gdbarch))
>> gdbarch_write_pc (gdbarch, regcache, pc);
>> else if (gdbarch_pc_regnum (gdbarch)>= 0)
>> regcache_cooked_write_unsigned (regcache,
>> gdbarch_pc_regnum (gdbarch), pc);
>> else
>> internal_error (__FILE__, __LINE__,
>> _("regcache_write_pc: Unable to update PC"));
>>
>> /* Writing the PC (for instance, from "load") invalidates the
>> current frame. */
>> reinit_frame_cache ();
>> }
>
> And gdbarch_pc_regnum is AARCH64_PC_REGNUM.
>
> So it looks like we shouldn't need aarch64_write_pc?
Thanks for the heads up; yes, aarch64_write_pc doesn't appear necessary.
I've prepared the attached patch to remove the function.
Thanks,
Yufeng
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 998 bytes --]
diff --git a/gdb/aarch64-tdep.c b/gdb/aarch64-tdep.c
index ebc78d6..2b03106 100644
--- a/gdb/aarch64-tdep.c
+++ b/gdb/aarch64-tdep.c
@@ -2499,14 +2499,6 @@ aarch64_pseudo_write (struct gdbarch *gdbarch, struct regcache *regcache,
gdb_assert_not_reached ("regnum out of bound");
}
-/* Implement the "write_pc" gdbarch method. */
-
-static void
-aarch64_write_pc (struct regcache *regcache, CORE_ADDR pc)
-{
- regcache_cooked_write_unsigned (regcache, AARCH64_PC_REGNUM, pc);
-}
-
/* Callback function for user_reg_add. */
static struct value *
@@ -2618,8 +2610,6 @@ aarch64_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches)
set_gdbarch_push_dummy_call (gdbarch, aarch64_push_dummy_call);
set_gdbarch_frame_align (gdbarch, aarch64_frame_align);
- set_gdbarch_write_pc (gdbarch, aarch64_write_pc);
-
/* Frame handling. */
set_gdbarch_dummy_id (gdbarch, aarch64_dummy_id);
set_gdbarch_unwind_pc (gdbarch, aarch64_unwind_pc);
next prev parent reply other threads:[~2013-04-17 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:36 Joel Brobecker
2013-04-17 17:07 ` Yufeng Zhang [this message]
2013-04-17 17:08 ` Joel Brobecker
2013-04-17 20:33 ` Yufeng Zhang
2013-04-17 20:33 ` Joel Brobecker
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=516EB29D.2030409@arm.com \
--to=yufeng.zhang@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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