Migrate C code to Rust
-
Updated
Nov 12, 2024 - Rust
Migrate C code to Rust
Checked C is an extension to C that lets programmers write C code with bounds checking and improved type-safety. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors.
Wrangling Untrusted File Formats Safely
This repo contains a version of clang that is being modified to support Checked C. Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe.
MesaLock Linux: a memory-safe Linux distribution.
This repository contains the CHERI extension specification, adding hardware capabilities to RISC-V ISA to enable fine-grained memory protection and scalable compartmentalization.
Lean C/C++ Bounds Checking with Low-Fat Pointers
A Fast and Safe Python based on PyPy
Safe, fast, zero-panic, zero-crashing, zero-allocation parsing of untrusted inputs in Rust.
Runtime type and bounds-error checking for C/C++
A binary hardening system
Configurable instrumentation of LLVM bitcode
R3-OS — Experimental static (μITRON-esque) RTOS kernel for deeply embedded systems, testing the limit of Rust's compile-time evaluation and generics
instrumentor is a tool for instrumenting LLVM IR to detect problems at runtime. The initial focus is on memory safety issues such as leaks, use-after-free, stack smashing, and out-of-bounds access.
In-memory security with secure data types
MIRROR of https://codeberg.org/catseye/Eightebed : A C-like language with explicit free which is nonetheless safe
Lists of must-read papers (mainly security papers)
Internal presentation about Rust, focused on memory safety and concurrency
C Compiler that strives to be as (memory) safe as possible.
Add a description, image, and links to the memory-safety topic page so that developers can more easily learn about it.
To associate your repository with the memory-safety topic, visit your repo's landing page and select "manage topics."