For a compiler which ostensibly has a register allocator that is wild. Why are x13 and x14 involved at all? Why is it moving the return into x13 at the end?
For a compiler which ostensibly has a register allocator that is wild. Why are x13 and x14 involved at all? Why is it moving the return into x13 at the end?
Claude’s C compiler is impressive in many ways, but the inefficiency of its codegen may be a little understated. For:
unsigned long foo(unsigned long a, unsigned long b) { return a + b; }
It generates the following arm64:
unfortunately the dune movie fired me as music supervisor. villeneuve rejected my vision of gradually making “sandstorm” by darude louder and louder
My younger brother is trans. My parents have been horrendous about deadnaming and misgendering him. At Thanksgiving, I used an air horn to correct them. I fixed a 2-3 year long problem in two seconds. 10/10 would recommend this training method.
This is the best bit of advice I’ve seen on the internet 😂