[Octave-bug-tracker] [bug #53713] test failure "speed.m" in Octave 4.3.91

[Rik]

Follow-up Comment #11, bug #53713 (project octave):

This function has always used wall time, so I don't know that we want to
change it more right now.

I expect, however, that things would be worse using cputime.  The problem is
already that some functions, like sum(), are so fast that the measured elapsed
time is zero.  On my Linux machine, with high precision timers, I get zero for
the sum() operation which is failing


octave:3> x = randn (100, 1);
octave:4> t1 = cputime; sum (x); t2 = cputime;
octave:5> t2 - t1
ans = 0


On a Windows machine this will definitely return 0.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53713>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/