Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No overflow/carry flag impacting safe overflow checking and bignum performance, the whole conditional move history and backpeddling and state of Zicond, the system for describing feature support is needlessly complicated and just a mess for users outside of embedded, the spec is written more like an academic paper than a CPU manual, vector instructions act like they're written for a coprocessor for some reason, bad frame pointer ABI support, etc.




>safe overflow checking

You mean rust? Rust uses unsigned integers for everything, they can be checked efficiently. Same for bignum.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: