3 ms·
The code produced by Clang is a direct translation of the C code. That's the obvious part of it Most people here are not familiar with x86 assembly and its cav
by raverbashing 9y ago
The code produced by Clang is a direct translation of the C code. That's the obvious part of it
Most people here are not familiar with x86 assembly and its caveats it seems. Reading the Intel and AMD optimization manuals might be a good start
(and yes, the bug is not in GCC it's on the Intel processor)
- acdha 9y ago> Most people here are not familiar with x86 assembly and its caveats it seems. Reading the Intel and AMD optimization manuals might be a good start. Please don't make unsupported assertions that everyone but you is speaking out ignorance. It doesn't add anything to the conversation, especially when dealing with older codebases unless you can prove that this is and never has been the correct way to write that code. Otherwise it's just another way to say “CPU optimizations change over time and an open-source project doesn't have a team of experts tracking microbenchmarks to decide when to switch”.
- raverbashing 9y agoShould be easy to prove me wrong if it's as easy as you say, I don't see why you're so annoyed by it > “CPU optimizations change over time and an open-source project doesn't have a team of experts tracking microbenchmarks to decide when to switch” Yes, that's what's happening, but the problem comes from the P6 architecture (though Netburst doesn't have those problems), this problem has been known for around 20 years