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

Triggers with action != 0 or 1 fire independently. #1070

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Triggers with action != 0 or 1 fire independently. #1070

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
7 changes: 4 additions & 3 deletions Sdtrig.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,9 +141,10 @@ and that a trigger set by user code doesn't affect the external
debugger. If this is not implemented, then the hart must enter Debug
Mode and ignore the breakpoint exception. In the latter case, {mcontrol-hit} of the
trigger whose action is 0 must still be set, giving a debugger an
opportunity to handle this case. What happens with trace actions when
triggers with different actions are also firing is left to the trace
specification.
opportunity to handle this case.
Since triggers that have an action other than 0 or 1 don't affect the execution
of the hart, they are not mentioned in the priority table. Such triggers fire
independently from those that have an action of 0 or 1.

[[nativetrigger]]
=== Native Triggers
Expand Down
Loading