From: Joel Brobecker <brobecker@adacore.com>
To: marcus.shawcroft@arm.com, yufeng.zhang@arm.com
Cc: gdb-patches@sourceware.org
Subject: unnecessary aarch64_write_pc ?
Date: Mon, 15 Apr 2013 16:36:00 -0000 [thread overview]
Message-ID: <20130415125021.GB3525@adacore.com> (raw)
Hello,
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?
I am reviewing the other definitions, and so far, they do seem to be
necessary.
--
Joel
next reply other threads:[~2013-04-15 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:36 Joel Brobecker [this message]
2013-04-17 17:07 ` Yufeng Zhang
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=20130415125021.GB3525@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=yufeng.zhang@arm.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