Comment by KolmogorovComp
1 day ago
It used to be the same with assembly. Programmers complained the one generated by compilers was not pretty, but now in 99.999% of the cases, it does not matter because nobody look at it.
1 day ago
It used to be the same with assembly. Programmers complained the one generated by compilers was not pretty, but now in 99.999% of the cases, it does not matter because nobody look at it.
I beg to differ because a compiler is deterministic.
Did you check? Do you care if it sometimes does mov ax, 0 or sometimes xor ax,ax? (Forgive my bad memory, it was a long time ago)
Would you personally vouch, at your job, for the importance of proper assembly coding standards?
I was more after the fact i can trust the compiler to give me the same result - even though via an optimized path.
Certainly scopes vary, but in my line of work i define memory layout and how this data will be processed myself - thus it's great a compiler might do that, but the result of the computation will not change.
Now in comparison giving an LLM specs ... i a) cannot be sure what the computation will be b) it might be something else on another run.
Yes, the same compiler generates the same output given the same input. I'd be willing to put a large amount of money on that result.
I read a lot of assembly.