I'd love to see mor in-depth tests.
These tests oftne land in "Meh, whatever" category, at least for me.
I would like to see more thought-out in-depth tests.
For example, whole point fo using gcc-4.7x for me is -flto optimisation.
It would be nice to see what it can bring to the table when compiling programs from many sources and compilation units which are then linked into final library and/or executeable.
Of course, right programm to test this is not something like tar but something more complex.
Also it would be nice to see and compare used resources and final result during flto compilation and linking. flto has been notorious for eating memory and CPU cycles when compiling chrome or openoffice. It would be nice to see how much has this impact with gcc-4.5* - gcc-4.8*
Also, when finding regressions, it would be nice to go in-depth for their cause. Is error on the part of compiler, or simply program infrastructure misunderstood some compilers new feature, for example ?