Hacker GitHub

← All repos

pizlonator/fil-c

View on GitHub ↗ ★ 3,898

Fil-C: completely compatible memory safety for C and C++

69 mentions on Hacker News by 48 people: 19 stories, 50 comments · first 2024-02-21 · latest 2026-10-27

Mentions per year 69 mentions · busiest year 2025 (36)
20082026
AllStoriesComments NewestTopOldest
  1. …it takes to port PHP to Fil-C and according to our tests this turns all of the exploits into DoS https://github.com/pizlonator/fil-c/blob/deluge/projects/php...
    comment by pizlonator · 2026-10-27 · in PHP2Shell: Exploitation attempts and remediation trends
  2. …call Phil's Concurrent Marking. I've documented it here: https://fil-c.org/fugc Here's the source: https://github.com/pizlonator/fil-c/blob/deluge/libpas/src/l... Phil's Concurrent Marking differs from DLG in that it only requires a…
    comment by pizlonator · 2026-10-05 · in A 40ms Go garbage collector pause caused by swap
  3. …and Apple (Manager of the JavaScriptCore Team). He seems to be the main developer of Fil-C: https://github.com/pizlonator/fil-c although there are other contributors.
    comment by zdimension · 2026-07-25 · in Fil-C: Garbage In, Memory Safety Out [video]
  4. Claude.md was added 8 months ago. https://github.com/pizlonator/fil-c/blob/deluge/CLAUDE.md
    comment by bitbasher · 2026-06-30 · in Memory Safe Context Switching
  5. https://github.com/pizlonator/fil-c/blob/deluge/libpas/src/l...
    comment by elitepleb · 2026-06-26 · in Gossamer: a Rust-flavoured language with real goroutines and pause-free memory
  6. …don't mention this aspect. [0] https://www.theregister.com/2024/11/16/rusthaters_unite_filc... [1] https://github.com/pizlonator/fil-c/blob/deluge/README.md
    comment by uticus · 2026-04-29 · in CJIT: C, Just in Time
  7. https://github.com/pizlonator/fil-c?tab=readme-ov-file#requi... says that the current implementation only targets Linux+x86_64 but that they see no reason it couldn't be portable. But you're in the wrong (sub)thread; this (sub)thread is…
    comment by yjftsjthsd-h · 2025-12-16 · in Rust Coreutils 0.5.0 Release: 87.75% compatibility with GNU Coreutils
  8. …Fil-C[1][2], that can provide memory-safety, with no to minimum changes to the code. [1]: fil-c.org/ [2]: github.com/pizlonator/fil-c
    comment by baranul · 2025-12-02 · in APT Rust requirement raises questions
  9. …Haha. Fil-c appears to already compile libxml2[1] so I wonder how far off libxslt would be? [1] https://github.com/pizlonator/fil-c/tree/deluge/projects/lib...
    comment by verytrivial · 2025-11-10 · in XSLT RIP
  10. …inline assembly for system calls with calls to libpizlo.so's syscall API. That links here: https://github.com/pizlonator/fil-c/blob/deluge/filc/include... Quotes from: https://fil-c.org/runtime
    comment by jitl · 2025-11-03 · in Notes by djb on using Fil-C
  11. …part is hard, and maybe I'll describe it in another post. Look for `filc_enter` and `filc_exit` in https://github.com/pizlonator/fil-c/blob/deluge/libpas/src/l...
    comment by pizlonator · 2025-09-05 · in Fil's Unbelievable Garbage Collector
  12. …will be the 100% memory safe C/C++ compiler, which is also implemented and works amazingly well: https://github.com/pizlonator/fil-c > It's not even possible to link to unsafe code. This makes it rather theoretical.
    comment by account42 · 2025-09-01 · in What to do with C++ modules?
  13. …will be the 100% memory safe C/C++ compiler, which is also implemented and works amazingly well: https://github.com/pizlonator/fil-c Again—do you expect the standards committee to enforce usage of this compiler or what? The standards…
    comment by throwawaty76543 · 2025-08-31 · in What to do with C++ modules?
  14. …will be the 100% memory safe C/C++ compiler, which is also implemented and works amazingly well: https://github.com/pizlonator/fil-c
    comment by modeless · 2025-08-31 · in What to do with C++ modules?
  15. …not just fail the intra-object OOB test, it would also fail the "out of bounds but in bounds" case: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by pizlonator · 2025-07-11 · in Evaluating the Effectiveness of Memory Safety Sanitizers
  16. Download binaries here: https://github.com/pizlonator/llvm-project-deluge/releases Try to port it. Maybe it'll just work
    comment by pizlonator · 2025-07-04 · in Introducing tmux-rs
  17. …It can compile real C projects like SQLite and OpenSSL with minimal to no changes, today. https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by modeless · 2025-06-30 · in The provenance memory model for C
  18. I wonder if fil c would make most of these issues go away https://github.com/pizlonator/llvm-project-deluge
    comment by leoh · 2025-06-27 · in Libxml2's "no security embargoes" policy
  19. > Even C/C++ can be made memory safe, cf. https://github.com/pizlonator/llvm-project-deluge > Fil-C achieves this using a combination of concurrent garbage collection and invisible capabilities (each pointer in memory has a corresponding…
    comment by vlovich123 · 2025-06-26 · in Why is the Rust compiler so slow?
  20. …Rust code just gets shoved into Unsafe blocks anyway. Even C/C++ can be made memory safe, cf. https://github.com/pizlonator/llvm-project-deluge What I'm more interested to know is what the runtime performance tradeoff is like now; one…
    comment by pixelpoet · 2025-06-26 · in Why is the Rust compiler so slow?
  21. …valid pointer." And sure enough, your runtime manually wraps each Linux syscall to do exactly that: https://github.com/pizlonator/llvm-project-deluge/blob/6804d... For harder cases like fcntl, where arguments can be either pointers or…
    comment by comex · 2025-05-14 · in How (memory) safe is Zig? (2021)
  22. …(each pointer in memory has a corresponding capability, not visible to the C address space) https://github.com/pizlonator/llvm-project-deluge/tree/delug...
    comment by Ygg2 · 2025-05-14 · in How (memory) safe is Zig? (2021)
  23. What's Fil-C? Okay, found it myself, looks cool: https://github.com/pizlonator/llvm-project-deluge/ What's yoyoland? All I can find is an amusement park in Bangkok, and some 1990s-era communication software for Classic Mac OS:…
    comment by skissane · 2025-05-10 · in Comparison of C/POSIX standard library implementations for Linux
  24. …like a capable approach to transpile C/C++ and add a managed runtime - and without much overhead. https://github.com/pizlonator/llvm-project-deluge/blob/delug... > The uncontrolled proliferation of undefined behavior is ultimately what is…
    comment by nayuki · 2025-05-07 · in Matt Godbolt sold me on Rust by showing me C++
  25. …even though there should be nothing preventing it from running on other platforms. [1]: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by reirob · 2025-04-28 · in Ask HN: Memory-safe low level languages?
  26. C can be memory safe now! https://github.com/pizlonator/llvm-project-deluge Yes, this is a real project that really works. It can compile real and widely used software written in C including SQLite, OpenSSL, and CPython, giving them true…
    comment by modeless · 2025-04-28 · in Ask HN: Memory-safe low level languages?
  27. …on improving Fil-C's stability and compatibility. Fil-C is a memory-safe implementation of C. https://github.com/pizlonator/llvm-project-deluge/blob/delug... You can try it easily on Linux/X86_64: https://github.com/pizlonator/llvm-project-…
    comment by pizlonator · 2025-04-28 · in Ask HN: What are you working on? (April 2025)
  28. …do checked addition / bounds checked access. There are even efforts to make this the case with C: https://github.com/pizlonator/llvm-project-deluge/blob/delug... achieves a ~50% overhead, far far better than Python. And even among…
    comment by achierius · 2025-04-09 · in An Overwhelmingly Negative and Demoralizing Force
  29. …actively working on performance optimizations for Fil-C, so that 4x number will go down." source https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by ape4 · 2025-03-13 · in Carefully but Purposefully Oxidising Ubuntu
  30. This is helpful as well because it at least alludes to the data structures: https://github.com/pizlonator/llvm-project-deluge/blob/delug... One more thing: I assume the memory allocator has a somewhat efficient way to recover the pointer…
    comment by fweimer · 2025-03-01 · in The need for memory safety standards
  31. How are the pointers implemented? See here: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by rurban · 2025-03-01 · in Just some of the memory safety errors caught by Fil-C
  32. BTW I wrote another doc to try to explain what's happening. Hope this helps. https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by pizlonator · 2025-02-28 · in The need for memory safety standards
  33. Here’s a write up that goes into more detail: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by pizlonator · 2025-02-27 · in The need for memory safety standards
  34. …for each pointer. Fil-C seems to be a C variant that adds capabilities and garbage collection. See https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by warkdarrior · 2025-02-26 · in The need for memory safety standards
  35. …attribute cleanup if you want to know more) and ifunc support. More info about the project here: https://github.com/pizlonator/llvm-project-deluge And a Linux/X86_64 binary release if you want to play with it:…
    comment by pizlonator · 2025-02-24 · in Ask HN: What are you working on? (February 2025)
  36. …coming solution that promises even more memory safety is Fil-C which is being made by Epic Games. https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by jart · 2024-12-31 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  37. Garbage collection handbook https://gchandbook.org/ If you want to see my latest concurrent GC, see https://github.com/pizlonator/llvm-project-deluge/blob/delug... https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by pizlonator · 2024-12-19 · in Borrow Checking, RC, GC, and Eleven Other Memory Safety Approaches
  38. …expertise required) and runtime hacking (experience with high level language runtimes required). https://github.com/pizlonator/llvm-project-deluge
    comment by pizlonator · 2024-11-16 · in Ask HN: What open source projects need help?
  39. …It’s not a new language, just a different way of implementing it. Here’s more info about Fil-C: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by pizlonator · 2024-11-01 · in Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk
  40. I think it’s this: https://2024.splashcon.org/details/splash-2024-rebase/3/Fil-... https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by orion138 · 2024-10-21 · in The empire of C++ strikes back with Safe C++ blueprint
  41. A worked example: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by Rusky · 2024-10-16 · in The C23 edition of Modern C
  42. https://github.com/pizlonator/llvm-project-deluge
    comment by sitkack · 2024-08-29 · in Formal CHERI: design-time proof of full-scale architecture security properties (2022)
  43. https://github.com/pizlonator/llvm-project-deluge/blob/delug... https://m.youtube.com/watch?v=JRoX9_lXJFg Note that both that doc and the video have old perf numbers. I’m landing optimizations all the time.
    comment by pizlonator · 2024-08-28 · in Formal CHERI: design-time proof of full-scale architecture security properties (2022)
  44. They do https://github.com/pizlonator/llvm-project-deluge/blob/delug... Or https://www.circle-lang.org/site/intro/
    comment by pizlonator · 2024-06-22 · in C can be memory safe
  45. I'm attempting something. https://www.youtube.com/watch?v=Gij9UQy_JEQ https://github.com/pizlonator/llvm-project-deluge/blob/delug... Right now I'm ~90% through a major rewrite to use GC instead of isoheaps, because then I'll go from…
    comment by pizlonator · 2024-04-04 · in Xr0: C but Safe
  46. …type at all. So one has to use indices everywhere. Why not just embrace isoheaps instead? [1] - https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by googh · 2024-03-27 · in Rust data structures with circular references (2021)
  47. …Why bother with Rust or any other language with borrow checkers then? Just a honest question. [1] - https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by googh · 2024-03-27 · in Rust data structures with circular references (2021)
  48. …people would like to run C code in the browser but don't want to bring memory unsafety there. link: https://github.com/pizlonator/llvm-project-deluge/blob/delug...
    comment by fulafel · 2024-03-14 · in C++ Safety, in Context
  49. …use memory-safe OpenSSL. https://github.com/pizlonator/deluded-openssl-3.2.0 It's based on Fil-C https://github.com/pizlonator/llvm-project-deluge/blob/delug... There's no unsafe code in it. The whole thing is recompiled with Fil-C. Works…
    comment by pizlonator · 2024-02-29 · in Memory Safe TLS Library Now Has AWS Crypto and FIPS
  50. See here: https://github.com/pizlonator/llvm-project-deluge/blob/delug... I just got the OpenSSH client to work last night. Here's an example of the kinds of changes you have to make: https://github.com/pizlonator/deluded-openssh-portable/c…
    comment by pizlonator · 2024-02-28 · in United States White House Report on Memory Safe Programming [pdf]