Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify why to use progbuf to access FPRs/CSRs #1067

Merged
merged 1 commit into from
Aug 27, 2024
Merged

Clarify why to use progbuf to access FPRs/CSRs #1067

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions debugger_implementation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,9 +101,9 @@ Write `mstatus` using abstract command:
[[deb:regprogbuf]]
===== Using Program Buffer

Abstract commands are used to exchange data with GPRs. Using this
mechanism, other registers can be accessed by moving their value
into/out of GPRs.
Abstract commands are only required to support GPR access. To access non-GPR
registers, the debugger can use the Program Buffer to move values to/from a GPR,
and then access the GPR value using an abstract command.

Write `mstatus` using program buffer:

Expand Down
Loading