[Bug build/7946] Doco 'jump' vs '$pc = ..., $npc = ....'

[Bug build/7946] Doco 'jump' vs '$pc = ..., $npc = ....'

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=7946

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d42948f0c822ed3782a45771c8fbc21aa2d6553

commit 0d42948f0c822ed3782a45771c8fbc21aa2d6553
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Mon Apr 24 15:27:27 2023 +0100

    gdb/doc: extend the documentation of the jump command

    This commit addresses PR gdb/7946.  While checking for bugs relating
    to the jump command I noticed a long standing bug that points out a
    deficiency with GDB's documentation of the jump command.

    The bug points out that 'jump 0x...' is not always the same as 'set
    $pc = 0x...' and then 'continue'.  Writing directly to the $pc
    register does not update any auxiliary state, e.g. $npc on SPARC,
    while using 'jump' does.

    It felt like this would be an easy issue to address by adding a
    paragraph to the docs, so I took a stab at writing something suitable.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=7946

    Approved-By: Eli Zaretskii <eliz@gnu.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug build/7946] Doco 'jump' vs '$pc = ..., $npc = ....'

[aburgess at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=7946

Andrew Burgess <aburgess at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED
                 CC|                            |aburgess at redhat dot com

--- Comment #2 from Andrew Burgess <aburgess at redhat dot com> ---
I believe this is now resolved.

-- 
You are receiving this mail because:
You are on the CC list for the bug.