-
Notifications
You must be signed in to change notification settings - Fork 196
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
Implement cuda::mr::cuda_memory_resource
#1578
Conversation
So my review is gone. Let's avoid "stacked PRs". Losing reviewer history is a big loss in productivity. |
It was more my bad. I forgot to change the target branch before I merged the first PR |
Also the review is still there #1513 |
2b30982
to
c701e83
Compare
libcudacxx/include/cuda/__memory_resource/cuda_memory_resource.h
Outdated
Show resolved
Hide resolved
Please respond to this unanswered comment: #1513 (comment) |
Addressed the comment |
5df98a1
to
7c86598
Compare
* @throw cuda::cuda_error of the returned error code | ||
* @return Pointer to the newly allocated memory | ||
*/ | ||
void* allocate(const size_t __bytes, const size_t __alignment = default_cuda_malloc_alignment) const |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Should allocate
in all our resources always be nodiscard
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
b367f31
to
83a2dd5
Compare
Fixes #1512
I managed to close #1513 because I did not change the target branch before merging
Stacked PRs are "fun"