3 ms·
My guess would be: yes, that generated slower code, at the time the code was written. A C compiler from the 1970's was almost little more than a glorified patt
by Someone 14y ago
My guess would be: yes, that generated slower code, at the time the code was written.
A C compiler from the 1970's was almost little more than a glorified pattern matcher. It easily could emit different code for "i += 1" vs "++i" vs "i++" (and that would not be a problem, as the C programmers used C as a replacement for assembly, and there, "INC R" is different from "ADD #1,R")
To check whether that theory holds water, one would have to check older SPEC benchmarks, to see where this fragments came from.
- mansr 14y agoThe code in question comes from the reference implementation of the H.264 video codec. What scraps of code this was cobbled together from is anyone's guess.
- cygx 14y agoI tracked it down to http://iphome.hhi.de/suehring/tml/download/old_jm/ http://iphome.hhi.de/suehring/tml/download/old_jm/ The bug is in version 9.3 used by SPEC CPU2006, but no longer in version 9.5. The current version is 18.4...