fil-c

This is all 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...

The classic on the fly GC algorithm is DLG, hilariously published in two papers, because the first one had a bug. Here's the second paper: https://caml.inria.fr/pub/papers/doligez_gonthier-gc-popl94.... It's a well known algorithm. Folks who do GCs for a living know about it. The folks who work on Go are surely aware of it. I'm assuming that they do not use it for a good reason, hence my question! Fil-C's GC (Fil's Unbelievable Garbage Collector) uses an alternative on-the-fly algorithm, which I 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 Djikstra barrier and uses a permagrey stack (something that Go used to do). However, FUGC does clever things for cor

Filip Pizło (https://www.filpizlo.com/), according to his website: Director of Programmability and Data Model at Roblox. Previously, I worked at Epic Games (Senior Director of Language Engineering) 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.

Claude.md was added 8 months ago. https://github.com/pizlonator/fil-c/blob/deluge/CLAUDE.md

> Definitely was not expecting this reference. Agreed, how HolyC serves as an inspiration could be clarified. Was it an aspect of HolyC? The background/context of the author's life, meaning Terry Davis was inspirational? Impossible to tell. Other resources [0] [1] 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

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 about whether it's safe.

> Honestly, rust is slightly more readable than obfuscated perl. > Rust is the kind of language that would push me to write a new language that isn't rust. It's wild how draconian and forced the use of Rust has become. It's one thing to be caught up in corporate induced hype, yet another level to force one's preferences or ideology on everybody else. Many people don't like Rust, for various acceptable reasons, and their right to choose should be respected. Sticking with C, is an equally acceptable option. In addition to there being various other newer C alternatives languages; with greater readability, memory-safety, and ease of use. There is also 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

Full of security issues is similarly overly dramatic, 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...

at the bottom of the turtle stack, there's a yolo-c libc that does some syscall stuff: > libyoloc.so. This is a mostly unmodified [musl/glibc] libc, compiled with Yolo-C. The only changes are to expose some libc internal functionality that is useful for implementing libpizlo.so. Note that libpizlo.so only relies on this library for system calls and a few low level functions. In the future, it's possible that the Fil-C runtime would not have a libc in Yolo Land, but instead libpizlo.so would make syscalls directly. but mostly you are using a fil-c compiled libc: > libc.so. This is a modified musl libc compiled with Fil-C. Most of the modifications are about replacing 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:/

> Note that the "safepointing" logic is exactly the same thing that's needed in refcounting to atomic replace a field. No it's not, not even close. > This article glosses over what I consider the hardest part - the enter/exit functionality around native functions may that block (but which must touch the allocator). Yeah, that 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...

> The next major advance to be completely ignored by standards committees 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.