Skip to content

Stop inspecting atomic_ref::fetch_or in Bloom filter checks - #832

Closed
PointKernel wants to merge 1 commit into
devfrom
fix-bloom-filter-word-type-check
Closed

Stop inspecting atomic_ref::fetch_or in Bloom filter checks#832
PointKernel wants to merge 1 commit into
devfrom
fix-bloom-filter-word-type-check

Conversation

@PointKernel

Copy link
Copy Markdown
Member

Per NVIDIA/cccl#10727, bloom_filter_impl no longer takes the address of cuda::atomic_ref::fetch_or to validate word_type. That check depends on the exact standard-library function form and breaks when P3323R1 is backported with constrained member templates. Since the Bloom filter uses native atomicOr, this PR checks the actual requirement instead: an integral 4- or 8-byte word type.

Validated against the current head of NVIDIA/cccl#10727; all 46 Bloom-filter test cases and 122 assertions pass.

@sleeepyjack

Copy link
Copy Markdown
Collaborator

Superseeded by #833

PointKernel pushed a commit that referenced this pull request Aug 14, 2026
This PR replaces the user-specified `Word` type in `bloom_filter_policy`
with a `WordBytes` parameter supporting 4- and 8-byte words. The policy
selects the corresponding native `atomicOr` type internally, preventing
users from supplying incompatible word types and removing the associated
validation and conversion machinery. By removing the stale
`cuda::atomic_ref::fetch_or` inspection, this also fixes the
cuCollections compatibility issue exposed by
[NVIDIA/cccl#10727](NVIDIA/cccl#10727) and
supersedes #832.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: bloom_filter Issues related to bloom_filter type: bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants