Amanieu

3 ms·

1.
by Amanieu 3y ago
The "proper" solution would be for apps to support 64-bit, at which point they can just run natively on the device. The whole reason Tango is required is that there is still a large number of apps that use 32-bit native libraries.
2.
by Amanieu 3y ago
When ARM released AArch64, it was a completely new instruction set rather than an extension of the existing 32-bit ISA (like x86-64). AArch64 is a much better designed ISA than AArch32 and supporting both in hardware effectively doubles the
3.
by Amanieu 3y ago
The first commit in what would eventually become Tango was all the way back in 2014, so this project has been in development for a long time. As such there have been many technical challenges. One challenge that particularly comes to mind w
4.
by Amanieu 3y ago
Hello HN! I'm the main developer behind the Tango binary translator. I'm happy to answer any questions you may have about the technology.
5.
by Amanieu 10y ago
I wrote an implementation of sequential locks in Rust [1]. It is extensively commented, which makes it a good way to learn how the algorithm works. [1] https://github.com/Amanieu/seqlock/blob/master/src&#
6.
by Amanieu 10y ago
The main downside of seqlocks is that you usually can't have pointers in them. Since the basic scheme is read, do stuff, check if sequence counter changed, you need to make sure that you don't dereference a potentially invalid poi
7.
by Amanieu 11y ago
That is a risk, which is why you need to block all signals using the sigprocmask syscall before unmapping your stack.
8.
Async++: a lightweight concurrency framework for C++11(github.com)
4 points by Amanieu 14y ago|0 comments