Choosing a Type‑Generic abs Implementation in C11 with _Generic Macros
Guide to choosing a type‑generic abs implementation in C11 using _Generic macros and inline functions, with trade‑offs, sample code, and verification steps.
Loading…
ReadMeFeed / Community knowledge
#c11
Real questions. Useful conversations. Find the people who know your stack.
cC11 Atomics: Lock-Free Shared State and Memory Ordering
C11 <stdatomic.h> provides standard atomic types and operations for thread-safe shared data. Learn how to use atomic counters and publication flags, choose correct memory orders, and verify lock-free support.
Using C11 _Generic to Write a Single Type‑Generic Math Macro
C11's _Generic keyword lets you write a single macro that expands to the correct float, double or long double math function, eliminating duplicated code.
Building a lock‑free integer counter with C11 _Atomic
Learn how to declare, initialize, and use a C11 _Atomic integer as a lock‑free counter, with compile commands, verification steps, and fallback options.
Designing a Type‑Generic abs Macro with C11 _Generic
Use C11 _Generic to create a zero‑overhead abs macro that selects the correct library function for int, long, float, and double arguments.
Using C11’s _Generic for Type‑Generic Macros
Learn how C11’s _Generic keyword lets you write a single type‑generic macro—illustrated with an abs() example—and understand its trade‑offs and verification steps.
Writing Type‑Generic Macros in C with _Generic
Learn how C11’s _Generic keyword lets you write a single, type‑safe macro that expands to the correct abs‑family function for int, long, float, or double, with zero runtime cost.
Data Race Undefined Behavior vs. False Sharing: Separating Concurrent-Only Latency Causes in C11 Handlers
Concurrent-only latency in a C11 request handler C11 defines a data race as undefined behavior: two threads access the same memory location, at least one access is a write, and no synchronization orders the operations. Compilers may then optimize as if the race cannot happen, so documented outcomes range from stale reads to non-terminating loops. This raises
Migrating to C18 with Optional VLA Support: Uncertain Runtime Impact
Goal We plan to upgrade a small C application that relies on Variable Length Arrays (VLAs) to C18 while keeping the service running. Constraints In C18 (C11), VLA support is optional; many compilers still provide it as an extension, but some omit it entirely. If a compiler silently removes VLA support, the program may allocate stack memory incorrectly, leadi