Tag
Apple has begun integrating Swift into the kernel via a new effort called KernelKit, with an Embedded Swift runtime appearing in macOS and iOS, marking a step toward memory-safe kernel extensions.
Fil-C introduces memory-safe inline assembly, ensuring that programmer errors result in panics or traps rather than miscompilation.
cuTile Rust introduces a tile-based programming model that leverages Rust's ownership to guarantee memory safety and data-race freedom for GPU kernels, and the Grout inference engine built on it achieves competitive throughput with vLLM/SGLang for Qwen3 models.
NVIDIA Labs releases cuTile Rust, a tile-based system for writing memory-safe, data-race-free GPU kernels in idiomatic Rust. It extends Rust's ownership model to GPU kernels, JIT-compiles Rust AST to GPU code, and achieves performance close to native CUDA.
An analysis of how memory safety CVEs are reported differently in Rust vs C/C++, arguing that Rust's design reduces certain classes of vulnerabilities even when bugs exist.
Apple migrated the TrueType hinting interpreter from C to Swift, achieving memory safety and a 13% performance improvement. The source code has been open-sourced.
Fil-C 0.679 is a new release of a fanatically compatible memory-safe implementation of C and C++ that uses concurrent garbage collection and invisible capabilities to prevent all memory safety errors without escape hatches.
This article introduces a new approach to memory safety based on linear types and abstract interpretation, aiming to eliminate common bugs like use-after-free and memory leaks more ergonomically than Rust.
Anthropic acquired Bun and used Claude Code agents to rewrite the entire runtime from Zig to Rust in nine days. The rewrite passed 99.8% of tests but introduced over 10,000 unsafe blocks, raising questions about the benefits of memory safety.
This article introduces iddqd, a Rust library that provides maps where keys are borrowed from values, reducing duplication and synchronization issues. It discusses the challenges of writing unsafe Rust code and how the library maintains correctness.
The author argues that memory-unsafe open-source software is critically vulnerable to upcoming AI bug-finding agents, making memory safety a moral imperative, and that Rust must succeed as the leading memory-safe language with no overhead.
Trifecta Tech Foundation announces the first release of libzstd-rs-sys, a pure Rust implementation of the Zstandard compression format, offering a drop-in replacement for the C reference implementation with improved portability and memory safety at a slight performance cost.
The article draws parallels between the security flaws in C/C++ and those in Verilog, arguing that the hardware description language's design leads to bugs and that the industry should invest in safer alternatives, similar to the push for memory-safe programming languages in software.
A deep dive into how a minimal, memory-safe Go implementation of rsync avoids a dozen vulnerabilities present in the original C version, with comparisons to OpenBSD's openrsync and defense in depth techniques.
Fil-C is a groundbreaking new programming language that promises to revolutionize the software ecosystem with memory safety.
A three-person team with AI assistance bypassed Apple's Memory Integrity Enforcement (MIE) in five days using two bugs and a clever idea, demonstrating a significant vulnerability in Apple's hardware-based kernel memory safety stack.
Microsoft announces a redesign of C#'s unsafe keyword in C# 16 to enforce memory safety contracts, making unsafe operations visible and compiler-enforced, with preview in .NET 11 and production in .NET 12.
An experienced C++ developer argues that all non-trivial C and C++ code contains undefined behavior, making memory safety impossible and calling into question the continued use of these languages in modern software development.
The Fil-C optimized calling convention ensures memory safety for C programs even under adversarial misuse, while maintaining efficiency by omitting safety checks in the common case. It explains the generic and register-passing optimizations that handle type violations via panics or well-defined behavior.
C++26 is introducing standardized library hardening to catch common undefined behavior (like out-of-bounds access) at runtime, based on Google's production experience showing a mere 0.30% performance overhead and a 30% reduction in segmentation faults.