{"id":1352,"date":"2009-04-06T19:49:05","date_gmt":"2009-04-07T02:49:05","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=1352"},"modified":"2010-01-24T18:28:54","modified_gmt":"2010-01-25T02:28:54","slug":"performance-smackdown-now-with-64-bit","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/performance-smackdown-now-with-64-bit\/","title":{"rendered":"Performance Smackdown, Now With 64-bit"},"content":{"rendered":"

Another in my continuing series of compiler performance reports– that is, the performance of straight C code when compiled by assorted compilers. Pursuant to round 3<\/a>, I downloaded the long, free, hi-def H.264\/AAC movie<\/a> to profile, as suggested by Reimar<\/a> and profiled that. It takes 11-15 minutes to decode the entire thing on my 2.13 GHz Core 2. No matter; my machine is patient, and here are the results:<\/p>\n


\n\"icc
\n<\/center><\/p>\n

“gcc-svn” is gcc 4.4.0-svn, revision 143046, built on 2009-01-03, same as before.<\/p>\n

All validations passed. Further, I used “march=pentium4” as suggested by Flameeyes<\/a>, on compilers that supported the option but not “march=core2” (gcc 3.4.6, 4.0.4, 4.1.2, and 4.2.4). I think that improved performance for those, but I won’t know for sure unless I run with the original MPEG-4 part 2\/MP3 movie from the previous tests.<\/p>\n

I also took this opportunity to see how native 64-bit builds performed on the same machine. I hope one day to get Intel’s 64-bit compiler working so it can be included in the competition:<\/p>\n


\n\"Profiling
\n<\/center><\/p>\n

For this test, I didn’t specify any compiler optimizations from the command line. Let me know if that should change for the next round. “gcc-svn” is a little more up to date at gcc 4.4.0-svn, revision 144720, built on 2009-03-08.<\/p>\n

Lingering TODO:<\/strong> Investigate if Acovea<\/a> can help in this process.<\/p>\n

See Also:<\/strong><\/p>\n