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.

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

Incorrect behaviour with INT_MAX pmpaddr #739

Open
Timmmm opened this issue Feb 14, 2025 · 0 comments
Open

Incorrect behaviour with INT_MAX pmpaddr #739

Timmmm opened this issue Feb 14, 2025 · 0 comments

Comments

@Timmmm
Copy link
Collaborator

Timmmm commented Feb 14, 2025

If you set pmpaddr to ones() then it will misbehave. For NAPOT it will return (zeros(), zeros()). For NA4 it will return (ones(), zeros()). In both cases it will match no addresses, whereas it should match all memory, or the top 4 bytes respectively.

I have a fix for this, and a test (I know!). The test is written in Zig... I was experimenting with that. I'll demo it in the next meeting I'm at (24th).

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

No branches or pull requests

1 participant