This is an interesting article, but as a Swift language designer, I'd really appreciate it if people didn't randomly throw out wildly inaccurate information like "Basically everything in swift is an Arc<Mutex<T>>".
Swift frameworks that use ObjC system libraries will still use objc_msgSend.
> Does iOS currently use different signature sizes? Code and data live in the same address space, and the address-space needs of the system are the main input to the basic signature width, so the basic signatures widths…
Right. Pointer authentication depends on it not being easy to forge a signature given the desired pointer. Given that there's a secret key included in the signature, the requirements on the hash function aren't really…
They can be compatible. Memory tagging does use the TBI bits. Pointer authentication uses an arbitrary number of bits, and the kernel configures the width and whether the TBI bits are preserved. So you can use both, it…
This is an interesting article, but as a Swift language designer, I'd really appreciate it if people didn't randomly throw out wildly inaccurate information like "Basically everything in swift is an Arc<Mutex<T>>".
Swift frameworks that use ObjC system libraries will still use objc_msgSend.
> Does iOS currently use different signature sizes? Code and data live in the same address space, and the address-space needs of the system are the main input to the basic signature width, so the basic signatures widths…
Right. Pointer authentication depends on it not being easy to forge a signature given the desired pointer. Given that there's a secret key included in the signature, the requirements on the hash function aren't really…
They can be compatible. Memory tagging does use the TBI bits. Pointer authentication uses an arbitrary number of bits, and the kernel configures the width and whether the TBI bits are preserved. So you can use both, it…