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
Put HPX_WITH_APEX in HPXConfig so out of tree projects can test for it #2346
Conversation
With this patch, direct actions are now always executed directly on the receiving side. This means that they might get executed in a non-HPX thread.
- hpx::compute::traits::allocator_traits didn't work with std::allocator<T> because it was using the pointer type instead of value_type for the initial value - hpx::compute::vector move operations lead to data being double freed because the move ctor didn't set the rhs data pointer to nullptr
This patch fixes problem in the channel implementation that led to locks being held during suspension.
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.
LGTM, thanks!
@biddisco Please isolate the APEX fix from all the other branches you merged into this (the direct actions branch, the vector zero copy branch, etc. are all separate PRs). |
I'm closing this PR as I have put wrong commits on the branch and I have some new APEX related changes that I'll bundle into a new PR |
@biddisco Can we delete this branch as well? |
No description provided.