3 ms·
This is yet another variant of the "fat pointers" technique, which has been implemented and rejected many times due to either insufficient security guarantees,
by vzaliva 5mo ago
This is yet another variant of the "fat pointers" technique, which has been implemented and rejected many times due to either insufficient security guarantees, inability to cross non-fat ABI boundaries, or the overhead it introduces.
- fooker 5mo agoThere’s a new wave of hardware supporting fat pointers natively, so you are perhaps dismissing it too early. Also filc isn’t just fat pointers.
- vzaliva 5mo agoHardware-supported capability-based architectures like CHERI are great. I am lilttle skeptical about adpotion prospects of software-only implementation of fat pointers for languages like C and C++.
- pjmlp 5mo agoHardware memory tagging has been available in several platforms now.