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

memcheck - clarify vector access #1664

Merged
merged 5 commits into from
Sep 26, 2024
Merged

memcheck - clarify vector access #1664

merged 5 commits into from
Sep 26, 2024

Conversation

jeremylt
Copy link
Member

@jeremylt jeremylt commented Sep 16, 2024

This PR tidies up the internals of the Memcheck CeedVector impl, making it clearer how we check access assumptions.

I then mirrored those changes into the QFunctionContext impl and threw in a bit of tidying for the QFunction too.

@jeremylt jeremylt force-pushed the jeremy/memcheck-tidy branch 3 times, most recently from bdb8f9d to 7e5ca22 Compare September 20, 2024 19:16
Copy link
Collaborator

@zatkins-dev zatkins-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall I think this clarifies memcheck behavior pretty well. I have some minor questions and a few suggestions, but otherwise this looks good.

backends/memcheck/ceed-memcheck-qfunction.c Outdated Show resolved Hide resolved
backends/memcheck/ceed-memcheck-qfunction.c Show resolved Hide resolved
backends/memcheck/ceed-memcheck-vector.c Show resolved Hide resolved
backends/memcheck/ceed-memcheck-vector.c Show resolved Hide resolved
backends/memcheck/ceed-memcheck-vector.c Show resolved Hide resolved
backends/memcheck/ceed-memcheck-vector.c Show resolved Hide resolved
@jeremylt jeremylt merged commit 8f302d0 into main Sep 26, 2024
23 of 24 checks passed
@jeremylt jeremylt deleted the jeremy/memcheck-tidy branch September 26, 2024 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants