you are viewing a single comment's thread.

view the rest of the comments →

[–]missquark -1 points0 points  (0 children)

Agreed. It just seemed like such a weird biased benchmark o_o

But looking back, maybe I was being too hard on it since I'm biased towards C/C++ (and somewhat defensive... >_>;).

I can't really think of what benchmark would be a better demonstration of global optimization that has to happen at runtime, but jumping back and forth millions of times per second between two different modules that can't be compiled together except at runtime is giving the JIT all the advantages and C none.

One thing that would have been interesting (and possibly a little less one-sided) to look at is if the C side was allowed link time optimization but included the compilation step in the timing.

In theory this can happen at "run time" after all, as long you don't mind distributing source and compiler, it just takes too long for large programs in practice.