-
Notifications
You must be signed in to change notification settings - Fork 89
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
Fix clang 17 compilation #394
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -443,7 +443,7 @@ __device__ | |
"insert_and_find is not supported for unpackable data on pre-Volta GPUs."); | ||
#endif | ||
|
||
auto current_slot{initial_slot(insert_pair.first, hash)}; | ||
auto current_slot{this->initial_slot(insert_pair.first, hash)}; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm trying to understand the logic here since we have many places missing There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would be genuinely surprised if this is the only place where we forgot to use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My suspicion is that this is the only code I am calling in my application and exercising. I need to go dig in and get you a real answer though, not a guess. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Make sense. @sleeepyjack we can merge the current PR as it is and fix other uncovered issues in your clang CI PR. What do you think? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm fine with that, especially if it unblocks @AustinSchuh 's work for now. |
||
|
||
while (true) { | ||
key_type const existing_key = current_slot->first.load(cuda::std::memory_order_relaxed); | ||
|
@@ -514,7 +514,7 @@ __device__ | |
|
||
// if we couldn't insert the key, but it wasn't a duplicate, then there must | ||
// have been some other key there, so we keep looking for a slot | ||
current_slot = next_slot(current_slot); | ||
current_slot = this->next_slot(current_slot); | ||
} | ||
} | ||
|
||
|
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.
@sleeepyjack
Just a reminder to ourselves,
thrust::pair
is the same ascuda::std::pair
so the current pair trait logic can be simplified.