3 ms·
Citation needed. I actually did the above (single stepped through the generated assembly from a few modern compilers) and I haven't noticed too much of a bad co
by acqq 16y ago
Citation needed. I actually did the above (single stepped through the generated assembly from a few modern compilers) and I haven't noticed too much of a bad code, given most of the default assumptions (i.e. to have a reasonably compatible code for different processors, to have the live entry points to the functions that are exportable etc.)
Maybe you looked at the code produced with the optimizations off?
- points 16y agoI've been reverse engineering code for a living for 10 years or so, and writing assembly code for 20 or so. I don't have the time to provide examples I'm afraid, so take it or leave it ;)
- acqq 16y agoI don't buy the argument from authority, I really think you're trolling. Apart from the bad FPU code in gcc 3 (or generally relatively poor code in gcc 3 compared to more recent or more expensive compilers) I really don't know examples of significant problems in the code generation of modern C compilers. Just don't give me examples that work only on the latest CPU's or that are fast only on one of CPU generations or on the CPU of only one manufacturer.