Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

posted multiple times, x86 only last time I checked




Yeah because I’m limiting my test matrix.

There’s nothing about how Fil-C is designed that constrains it to x86_64. It doesn’t strongly rely on x86’s memory model. It doesn’t strongly rely on 64-bit.

I’m focusing on one OS and arch until I have more contributors and so more bandwidth to track bugs across a wider set of platforms.


Hey Filip – while we're talking about memory architecture, have you started looking at ARM's EMTE extension (e.g https://security.apple.com/blog/memory-integrity-enforcement...)? Could it eventually replace invisicaps?

No. MTE is probabilistic. Fil-C is deterministic.

If you're taking votes, I would vote for AArch64 next. :D

noted :-)

Another vote for same.

All the more reason to make it portable. I wonder if this can be implemented via LLVM?

It is implemented via LLVM.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: