Are we fast yet?

[Dimitrios Apostolou]

Hello,

On Thu, 28 Jun 2012, Dimitrios Apostolou wrote:
>
> http://teras-ics.mooo.com:8003/
>

I've updated the page with some more measurements, please let me know what 
you think.

The primary issue I've not been able to resolve is with function name
demangling: Valgrind uses libiberty's demangler, which gives 
non-consistent names to functions. For example some functions are 
name-only-no-parentheses (glibc ones), others are 
name-with-empty-parentheses. Others are name-parens-with-args and others 
also have a [constprop.7] like thing in brackets. (I do all compilations 
with -O2 -fno-inline, I believe this has something to do with it).

You can see a visible effect of this issue on the last graph that shows 
the ten hottest functions, in particular record_reg_classes: before 
gcc-4.8.20120513 the function name was being demangled to a different name 
than afterwards, so it is plotted as it was zero before then. Demangled 
names:

before 20120513: record_reg_classes(int, int, rtx_def**, machine_mode*, char const**, rtx_def*, reg_class*) [clone .constprop.7]
after 20120513 : record_reg_classes(int, int, rtx_def**, machine_mode*, char const**, rtx_def*, reg_class*) [clone .constprop.6]

What do you think?


I've got some more ideas about information to add. Primarily I want to add 
a C++ testcase. In the past I've got some feedback about Boost.Spirit 
being very template-heavy and stressful for GCC, but I'd prefer to add a 
testcase from within the GCC tree, do you have something in mind?

Finally what do you think on hosting this page on gcc.gnu.org, after 
improving the details left? Maybe we can give it a dedicated subdomain: 
arewefastyet.gcc.gnu.org. From the technical point of view I need CGI, 
python3 and restricted SFTP access to upload new data regularly.


Thanks,
Dimitris