undefined | Better HN

0 pointsndesaulniers3mo ago0 comments

Or perhaps a `--target` flag that says "I'm targeting the linux kernel, not userspace, libcall these symbols (existing kernel functionality) rather than those (glibc interfaces)."

0 comments

pizlonator3mo ago

That won't solve it. Fil-C's memory safety relies on the Fil-C runtime

ndesaulniersOP3mo ago

Just as the sanitizers have a runtime, the linux kernel has a re-implementation of those runtimes (the linux kernel does not link libgcc/compiler_rt) and IIRC the compiler will work differently (I forget which flags control that). Prior art here.

pizlonator3mo ago

The sanitizer runtime is not nearly as complex as the Fil-C runtime.

Sanitizers don't have to deal with:

- https://fil-c.org/fugc

- 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

1 more reply

j / k navigate · click thread line to collapse