Conversation
pizlonator
reviewed
Apr 22, 2026
Member
Author
|
@pizlonator In our next release, we shall support building CRoaring with Fil-C. Ideally, we would have CI tests. But... it should be trivial from now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for building CRoaring with Fil-C, the memory-safe C compiler.
Fil-C instruments code for runtime memory safety (bounds checking, use-after-free prevention, etc.) via invisible capabilities and concurrent GC. While highly compatible, it is stricter than regular Clang/GCC in several areas, especially around:
Changes
Use special code for CPU dispatching when building with Fil-C.
Disable or wrap inline assembly that Fil-C cannot safely instrument.
Most of the hand-written SIMD assembly (AVX2/AVX-512) is now skipped under Fil-C.
Fix several warnings and minor issues unrelated Fil-C.