Any idea if it runs on real hardware ?
The only thing standing in the way of it working on real HW is just making sure the kernel is configured properly for it. Like right now the kernel config file is the result of enabling those things that work on the virtual devices that HyperV and VMware provide.
The right answer is modular kernel and something like initramfs and modprobe or whatnot. That kind of work has nothing to do with Fil-C; it’s just distro engineering
Fil, you can compile the Linux kernel will clang+lld. `make LLVM=1` https://docs.kernel.org/kbuild/llvm.html
So if I used clang, then I'd have three compilers (yolo-clang, gcc, fil-clang) instead of two (gcc, fil-clang).
Does the fil-c runtime depend on specifics from glibc, or is it that LFS doesn't support building with musl?
> We need to retain the Yolo GCC for compiling the Linux kernel.
Probably can replace that with s/the Linux kernel/glibc/. glibc maintainers have started upstreaming patches for building glibc with clang, but not sure yet what's the latest on that (large) patch series.
No. I could add a flag like that, but that would make my patch to clang larger, which would make rebasing to new clang versions harder.
So I'm choosing not to add such a flag. For now.
> Do you depend on glibc, or is it that LFS doesn't support building with musl?
I support both glibc and musl.
LFS is glibc-based.
Sanitizers don't have to deal with:
- https://fil-c.org/safepoints
Oh and it's not clear if the current revision of the capability model would work with memory mapped IO: https://fil-c.org/invisicaps
metadope•2d ago
pizlonator•1h ago