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!

>>60
You're braindamaged if you think that OpenGL does floating point divisions of two constants in a loop and nothing else. You can benchmark an OpenGL program that you port to multiple languages and see if you run into any differences. There already are implementations of things like glxgears in most languages with OpenGL bindings, so it's not like you would have to write any real code.
But if you think timing a million divisions in a loop is the same thing as benchmarking a whole OpenGL program, as if the entire doing graphics thing is non-important to the sight of floating point divisions (_{of constants}), that would explain everything.

>>61
You're paraphrasing >>60.