Fix ETMv4 exception return P0 handling for all M-profiles#90
Open
sayhal01 wants to merge 1 commit into
Open
Conversation
…cores Treat ETMv4 Exception Return packets as P0 elements for all Cortex-M profiles, not just v7-M. The ETMv4 specification defines Exception Return as a P0 element for M-profile architectures, including v6-M, v7-M and v8-M. Add regression snapshot tests covering both v7-M and v8-M exception return scenarios to validate the behavior and prevent future regressions. Signed-off-by: Sayani Halder <sayani.halder@arm.com>
sayhal01
force-pushed
the
dscore-26818-v8m-exception-return-p0
branch
from
af051f3 to
ec3b5dd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
-Treat ETMv4 Exception Return packets as P0 elements for all Cortex-M profiles, not just v7-M. The ETMv4 specification defines Exception Return as a P0 element for M-profile architectures, including v6-M, v7-M, and v8-M.
-Add regression snapshot tests covering both v7-M and v8-M exception return scenarios to validate the behavior and prevent future regressions.