Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
1–5 of 5 posts
Re: Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
#2From Fil Pizlo (http://www.filpizlo.com/), major contributor to WebKit's JavaScript engine, among other things:
> Fil-C is already powerful enough to run a memory-safe curl and a memory-safe OpenSSH (both client and server) on top of a memory-safe OpenSSL, memory-safe zlib, memory-safe pcre (which required no changes), memory-safe CPython (which required some changes and even found a bug), memory-safe SQLite, memory-safe libcxx and libcxxabi, and memory-safe musl (Fil-C's current libc).
Re: Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
#3Kudos for effort but some dealbreakers here. Hope it makes more progress.
Currently about 10x slower than standard C (ranging from 3x to 20x)
Only works on Linux/X86_64Re: Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
#4Kudos for effort but some dealbreakers here. Hope it makes more progress. Currently about 10x slower than standard C (ranging from 3x to 20x) Only works on Linux/X86_64
In his talk at REBASE, Fil said the overhead is now 1.5x to 5x, and he is just getting started optimizing.
Re: Fil-C: Memory-Safe and Compatible C/C++ with No Unsafe Escape Hatches
#5Kudos for effort but some dealbreakers here. Hope it makes more progress. Currently about 10x slower than standard C (ranging from 3x to 20x) Only works on Linux/X86_64
In his talk at REBASE, Fil said the overhead is now 1.5x to 5x, and he is just getting started optimizing.