-
Notifications
You must be signed in to change notification settings - Fork 908
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
[REVIEW] Verify that concatenating columns does not overflow size_type #6809
[REVIEW] Verify that concatenating columns does not overflow size_type #6809
Conversation
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
Codecov Report
@@ Coverage Diff @@
## branch-0.17 #6809 +/- ##
============================================
Coverage 81.94% 81.94%
============================================
Files 96 96
Lines 16164 16164
============================================
Hits 13246 13246
Misses 2918 2918 Continue to review full report at Codecov.
|
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, just have a small question.
…e logic for how it guarded offset columns didn't end up mattering.
// these pragmas work around the nvcc issue where if a column_view is used | ||
// inside of a __device__ code path, these functions will end up being created | ||
// as __host__ __device__ because they are explicitly defaulted. However, if | ||
// they then end up being called by a simple __host__ function | ||
// (eg std::vector destructor) you get a compile error because you're trying to | ||
// call a __host__ __device__ function from a __host__ function. |
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.
are we able to use constexpr for these constructors, instead? that would allow them to be used interchangeably.
When concatenating large columns, it is possible to overflow the max size of a column (size_type). We need to verify this won't happen ahead of time. Previously, we were doing it for non-nested types, and only in the fused kernel concatenation case. This addresses both issues.