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

MatrixFree: Use separate data arrays for two separate evaluators #14153

Merged
merged 1 commit into from Jul 20, 2022

Conversation

kronbichler
Copy link
Member

As discussed in #14152 (comment), we should use two separate arrays for two evaluators. Their use does not overlap, so the old code was not wrong, but if we decide to re-allocate memory on the second evaluator for some reason in the future, the first one will have pointers to free'd memory.

Copy link
Member

@tjhei tjhei left a comment

Choose a reason for hiding this comment

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

Can you please update the comment directly above?

@kronbichler
Copy link
Member Author

Right, I didn't realize this. 😉

@tjhei tjhei merged commit 8d81f9f into dealii:master Jul 20, 2022
@kronbichler kronbichler deleted the separate_array branch July 20, 2022 19:49
mkghadban pushed a commit to OpenFCST/dealii that referenced this pull request Sep 8, 2022
MatrixFree: Use separate data arrays for two separate evaluators
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.

None yet

4 participants