You DO know that script has been written in 1991, and computing power has increased by a factor of 2 every 18 months since then (according to Moore's Law). This means that (if I didn't use the wrong calculation formula) a loop that took 1 second then has to be run about 10000 times (give or take). The loops used in your benchmark finish so fast, that any calculation using the time expired (like line 38ff in your script) may as well use zero.
Use the input you have a few thousand times over, and you might get results, maybe even slightly meaningful ones. Or if it's just raw CPU power you're interested in, calculate Pi to a few thousand digits after the decimal point. That way, if you finish too fast, just add a few.
yes, I was aware that the error is in line 38 of the script... But I wanted to know why that was happening... Why the variable is getting a zero in it...
I just got the binaries and tried to execute it... I'll check if there's a newer version of it...