CRoaring
ck
CRoaring | ck | |
---|---|---|
8 | 7 | |
1,456 | 2,295 | |
1.6% | 0.4% | |
8.9 | 6.9 | |
about 21 hours ago | 19 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CRoaring
-
(Don't) crank up the warnings to 11
The PR in question seems to be https://github.com/RoaringBitmap/CRoaring/pull/446
I agree that the GitHub analyses are worse than useless, but I also think it highlights the friction between intrinsics and the program in which they appear. There probably is a better model.
-
Progress in building an 100% rust lang program.
Installation completed the program build successfully!! https://www.reddit.com/r/openbsd/comments/yux513/comment/iwbm72c/?context=3 I configured 2 different files in .cargo (thanx @ivan_linux for https://github.com/RoaringBitmap/CRoaring/pull/412) and .profile ( https://rust-lang.github.io/rust-bindgen/requirements.html#openbsd ) But when I try to start the program unfortunately the node not starting and I get the following errors.
- I will need your help to complete (if possible) a rust lang program installation
- What std::bitset could have been
-
How do Games manage NPC schedules?
I use a fake database paired with compressed bits for flags and integer compression for various other traits. They follow a navigation guide similar to wind for foliage.
-
Help with CFFI, C struct decoding, best practices / portability
I've been using CFFI to access the CRoaring C API to Roaring Bitmaps. It's been pretty easy so far. However I'm not experienced in lisp FFI, and I'm unsure of the way to go about the task of decoding a C structure used for iteration in the C CPI. The structure is as follows: ``` typedef struct roaring_uint32_iterator_s { const roaring_bitmap_t *parent; // owner int32_t container_index; // point to the current container index int32_t in_container_index; // for bitset and array container, this is out // index int32_t run_index; // for run container, this points at the run
-
FFI advice sought
I have a build shared library build of the C API for Roaring Bitmaps and I'm just trying to figure out the right path forward to write a lisp interface to it on sbcl.
-
C Deep
CRoaring - C implementation of Roaring bitmaps. Apache-2.0
ck
-
Falsehoods programmers believe about undefined behavior
Maybe I'm missing something, but x is not volatile and the compiler is free to assume that it is not modified concurrently outside the bounds of C's memory model. Compilers can and do hoist out loop invariants, and https://github.com/concurrencykit/ck/commit/b54ae5c4ace9b94442bbb46858449069f566d269 seems like an example of compilers doing what you say they don't. What am I missing?
- Concurrency Kit
-
A portable, license-free, lock-free data structure library written in C.
Recommend checking out http://concurrencykit.org instead.
-
Does a thread have a better chance of acquiring a mutex if it's just in time? Or if it's been in the queue? Neither?
If you're interested in how other approaches work, or how one achieves concurrency on shared mutable state without mutual exclusion, would recommend checking out concurrency kit.
-
Libdill: Structured Concurrency for C (2016)
There are plenty of practical solutions to the safe memory reclamation problem in C. The language just doesn't force one on you.
From epoch-based reclamation (https://github.com/concurrencykit/ck/blob/master/include/ck_..., especially with the multiplexing extension to Fraser's classic scheme), to quiescence schemes (https://liburcu.org/), or hazard pointers (https://github.com/facebook/folly/blob/master/folly/synchron..., or https://pvk.ca/Blog/2020/07/07/flatter-wait-free-hazard-poin...)... or even simple using a type-stable (https://www.usenix.org/legacy/publications/library/proceedin...) memory allocator.
In my experience, it's easier to write code that is resilient to hiccups in C than in Java. Solving SMR with GC only offers something close to lock-freedom when you can guarantee global GC pauses are short enough... and common techniques to bound pauses, like explicitly managed freelists land you back in the same problem space as C.
-
C Deep
ck - Concurrency primitives, safe memory reclamation mechanisms and non-blocking data structures. BSD-2-Clause
-
Super-expressive – Write regex in natural language
Indeed they do, https://github.com/concurrencykit/ck
What are some alternatives?
ZLib - A massively spiffy yet delicately unobtrusive compression library.
libcds - A C++ library of Concurrent Data Structures
C-album - An album of C code to study and investigate.
libdill - Structured concurrency in C
TurboPFor - Fastest Integer Compression
moodycamel - A fast multi-producer, multi-consumer lock-free concurrent queue for C++11
better_bitset - A better `std::bitset` that supports scanning for bits optimally
Thrust - [ARCHIVED] The C++ parallel algorithms library. See https://github.com/NVIDIA/cccl
gvsbuild - GTK stack for Windows
HPX - The C++ Standard Library for Parallelism and Concurrency
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
CUB - THIS REPOSITORY HAS MOVED TO github.com/nvidia/cub, WHICH IS AUTOMATICALLY MIRRORED HERE.