Tag
This paper presents a zero-overhead, multi-vendor GPU compilation framework built into the Rust compiler, leveraging Rust's ownership model to ensure memory safety and achieve competitive performance with native CUDA and HIP baselines.
The article discusses the internal conflicts within the C++ community regarding ABI breaks and memory safety, alongside government warnings and big tech companies shifting towards Rust.
This article evaluates the 'Rewrite It In Rust' movement in 2026, discussing real-world performance gains, challenges like new bugs and platform support, and advocating for incremental rewriting over full rewrites.
The author argues for a Rust FFI that speaks the Fil-C ABI, enabling safe interop with recompiled C/C++ libraries, and calls for cross-ecosystem collaboration among Rust, Fil-C, Zig, and Nix/filnix communities.
David Chisnall presents CHERI, a hardware capability architecture enabling memory safety and fine-grained compartmentalization through ISA extensions such as ARM Morello, RISC-V, and CHERIoT microcontrollers. The talk emphasizes the importance of practical programming models for secure isolation.
The article discusses the recent proposal for memory safety in Zig via Fil-C, compares Fil-C's definition of memory safety with Rust's, and argues that memory safety is a spectrum with practical definitions, using a concrete example where Fil-C is still unsafe.
SCI Semiconductor announces the first silicon implementation of CHERIoT, a RISC-V-based security architecture providing deterministic memory safety and compartmentalization. The ICENI chip runs at up to 250 MHz and will be demonstrated at Embedded World.
Intel highlights how its Control-Flow Enforcement Technology (CET) blocks exploitation of a 17-year-old remote code execution vulnerability in FreeBSD that was autonomously discovered and exploited by Anthropic's AI system Mythos.
C++26 introduces changes to reduce undefined behavior, notably making it ill-formed to delete a pointer to an incomplete type, improving program safety.
This article discusses strategies for migrating C/C++ projects to Rust, emphasizing incremental migration over full rewrites, with insights from Luca Palmieri and JetBrains.
The article critiques memory safety absolutism in programming language debates, arguing that new approaches like Fil-C have trade-offs and that dismissing Rust as unsafe ignores practical benefits.
Fil-C is a fully memory-safe implementation of C/C++. It bundles pointer values with boundary information using invisicaps at the LLVM IR stage, achieving high compatibility with a performance penalty of about 4x.
Describes Fil-C's InvisiCaps capability model for ensuring memory safety in C and C++ by tracking pointer permissions, while aiming for fanatical compatibility and reasonable performance.
This paper presents a modified Rust compiler for the Morello capability hardware architecture, enabling always-on memory safety even in unsafe code by leveraging hardware capabilities.
This article discusses a fundamental memory safety challenge involving tagged unions where a pointer to one variant is used after the union is overwritten with a different variant, leading to type confusion. The author also argues that buffer overflows are the most exploitable memory error and could have been mitigated with better array syntax.
A critique of null-terminated strings in C, arguing that length-based strings are superior for modern programming, leading to fewer bugs and better performance.
Jarred Sumner details the agentic rewriting of Bun from Zig to Rust using AI, costing $165k in tokens and resulting in a 10% faster startup.
Fil-C introduces memory-safe implementation of setjmp/longjmp and ucontext APIs, preventing dangling stack corruption and panicking on misuse.
OpenAI engineers detail the diagnosis of seemingly impossible crashes in Rockset's C++ data infrastructure, revealing both a silent hardware corruption bug on Azure and an 18-year-old race condition in GNU libunwind, resolved through epidemiological analysis of crash data.
Explains the `std::pin::Pin` type in Rust, why pinning is needed for self-referential types like async state machines, and how `Pin` prevents moves while allowing safe mutation.