Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* unnecessary aarch64_write_pc ?
@ 2013-04-15 16:36 Joel Brobecker
  2013-04-17 17:07 ` Yufeng Zhang
  0 siblings, 1 reply; 5+ messages in thread
From: Joel Brobecker @ 2013-04-15 16:36 UTC (permalink / raw)
  To: marcus.shawcroft, yufeng.zhang; +Cc: gdb-patches

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-04-17 15:10 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-15 16:36 unnecessary aarch64_write_pc ? Joel Brobecker
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox