hrtuhturht

Python:

time echo "for i in range(100000000): b = 3.14159265 / 1.161803399" | python

real    1m12.866s
user    1m11.549s
sys    0m0.160s

Ruby:

time echo "100000000.times do b = 3.14159265 / 1.161803399 end" | ruby

real    1m6.056s
user    1m5.952s
sys    0m0.047s

C:

benchmark.c:

int main(){
    double a;
    int x;
   
    for (x = 0; x < 100000000; x++)
    a  = 3.14159265 / 1.161803399;
}

Compilation:


time make benchmark
cc -ansi -pedantic -std=c1x  -lglut -lGLU -lrt  benchmark.c   -o benchmark

real    0m1.865s
user    0m0.240s
sys    0m0.073s

Run:

time ./benchmark

real    0m0.727s
user    0m0.630s
sys    0m0.007s

lol!

>>33
If you really wanted to know how much you shouldn't be doing things like these because they are pointless. Real code does not do things like this at all, and there is a reason gcc's optimizations take away all the code (it's pointless and does nothing). Maybe try making a program that does real work and port it to other languages for comparison, if you really wanted to waste your time but do the ``Right Thing'' instead.
_{IHBT, because I replied.}

>>34
I don't think you understand that the gcc optimization is referring to >>9.