Robert Dewar <de...@adacore.com> writes: > > Sure you can run some benchmarks and look for missed optimization > opportunities, that's always worth while, for instance people > regularly compare gcc and icc to look for cases where the gcc > optimization can be improved
OT, but there's lots of cool data on all of this on http://embed.cs.utah.edu/embarrassing/dec_09/ I spent some time some time ago to file a few "missed optimizations" bugzillas based on examples there and some got addressed. I'm sure there are lots more nuggets in there (as in easy cases to improve gcc), but analyzing each example takes time. The reason each sample takes time to analyze is that it is sometimes a bug in the other compiler or different target options or so. Sometimes it's also undefined code. Yes there are plenty of bugs in there, but I didn't find any for gcc at least (but only looked at a relatively limited set) -Andi -- a...@linux.intel.com -- Speaking for myself only.
