Skip to content

fix access to vector context#19

Merged
aap-sc merged 3 commits intosyntacorefrom
aap-sc/rvv_fixups
Jan 29, 2026
Merged

fix access to vector context#19
aap-sc merged 3 commits intosyntacorefrom
aap-sc/rvv_fixups

Conversation

@aap-sc
Copy link
Collaborator

@aap-sc aap-sc commented Jan 29, 2026

This MR fixes various issues raising from erroneous caching policy and incorrect restoration of vstart when accessing vector registers.

@aap-sc aap-sc force-pushed the aap-sc/rvv_fixups branch 2 times, most recently from 616532e to 9631dde Compare January 29, 2026 17:52
Based On: https://review.openocd.org/c/openocd/+/9414

When VTYPE is updated:

- VL is set to some appropriate value
- VSTART is set to zero

Signed-off-by: Anatoly Parshintsev <anatoly.parshintsev@syntacore.com>
Based on: https://review.openocd.org/c/openocd/+/9415/2

read access should not ruin the current execution context

Signed-off-by: Anatoly Parshintsev <anatoly.parshintsev@syntacore.com>
Based On: https://review.openocd.org/c/openocd/+/9416/2

Writes to the vtype register are expected to have the side effect of
resetting vl and vstart. However, the current implementation caches the
vtype state on read, which prevents subsequent writes with
already-cached values from being issued.

Signed-off-by: Anatoly Parshintsev <anatoly.parshintsev@syntacore.com>
@aap-sc aap-sc force-pushed the aap-sc/rvv_fixups branch from 9631dde to a0dca25 Compare January 29, 2026 18:49
@aap-sc aap-sc merged commit 19c10ae into syntacore Jan 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants