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

No-move memcpy #232

Open
corbett5 opened this issue May 2, 2021 · 0 comments
Open

No-move memcpy #232

corbett5 opened this issue May 2, 2021 · 0 comments

Comments

@corbett5
Copy link
Collaborator

corbett5 commented May 2, 2021

Definitely since it can avoid a move. I think the best way to do this is have registerTouch allocate in the given space if it didn't already exist and then touch it there. That way all memcpy has to do is replace move( space, true ) with registerTouch( space ). I don't really want to add that to this PR though so I'll create an issue.

Originally posted by @corbett5 in #231 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant