4 ms·
posted multiple times, x86 only last time I checked
by synergy20 1y ago
posted multiple times, x86 only last time I checked
- lambdaone 1y agoAll the more reason to make it portable. I wonder if this can be implemented via LLVM?
- kragen 1y agoIt is implemented via LLVM.
- pizlonator 1y agoYeah 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.
- khamidou 1y agoHey 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/ https://security.apple.com/blog/memory-integrity-enforcement...)? Could it eventually replace invisicaps?
- pizlonator 1y agoNo. MTE is probabilistic. Fil-C is deterministic.
- erichocean 1y agoIf you're taking votes, I would vote for AArch64 next. :D
- pizlonator 1y agonoted :-)
- jacquesm 1y agoAnother vote for same.