[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Rik
Subject: [Octave-bug-tracker] [bug #53713] test failure "speed.m" in Octave 4.3.91
Date: Mon, 23 Apr 2018 14:37:21 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]