A hard requirement for ABI compatibility cripples these kinds of mitigations whether it's CFI, bounds safety or temporal safety.
Hardware shouldn't even be involved. It's about grasping at ways to monopolize the cpu/isa market, not protecting users.
-
-
Thank you for knowing my goals and motivations better than I do. They may be different than
-
... the reasons for ARM to pick them up. Still it is an exciting primitive and hopefully fills a gap.
-
It's a probabilistic mitigation in direct conflict with an existing probabilistic mitigation for entropy. Improving one hurts the other.
-
It's a weal mitigation too. Ignoring the probabilistic aspect (pretend it's a high strength crypto signature), it's not enforcing that much.
End of conversation
New conversation -
-
-
Memory safety is completely achievable in general purpose computing. No need for wacky proprietary isa extensions that competing isas lack.
-
sure, lets wait for industry wide consensus across all ISAs before changing anything.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.