Fix compile warning from CUDF_FUNC_RANGE in a member function #11798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Compile warning was introduced in #11652 in
bgzip_data_chunk_source.cu
. The warning can be seen here https://gpuci.gpuopenanalytics.com/job/rapidsai/job/gpuci/job/cudf/job/prb/job/cudf-cpu-cuda-build/CUDA=11.5/12417/consoleFull (search for177-D
)The
nvtx3_range__
is part of theCUDF_FUNC_RANGE()
macro. The warning is incorrect and likely a compiler bug. The workaround in this PR is to add[[maybe_unused]]
to the variable declaration.I was not able to create a small reproducer for compile bug filing.
Checklist