cputime for Windows octave-2.9.16s is strange

[Tatsuro MATSUOKA]

Sorry

> For the cygwin octave-2.9.16 and MSVC octave-2.9.16, the cputime is correct.  
For the cygwin octave-2.9.16 and MSVC octave-2.9.15, the cputime is correct.

'MSVC octave-2.9.15' is correct.
--- Tatsuro MATSUOKA <address@hidden> wrote:

> Hello
> 
> cputime for Windows octave-2.9.16s is strange 
> 
> MSVC octave-2.9.16 by Michael
> octave.exe:3> ts=cputime();
> octave.exe:4> for n=1:1000;1==1;end;
> octave.exe:5> cputime()-ts
> ans =  62500
> 
> mingw octave-2.9.16 by Tatsuro
> octave.exe:3> ts=cputime();
> octave.exe:4> for n=1:1000;1==1;end;
> octave.exe:5> cputime()-ts
> ans =  93750
> 
> cygwin octave-2.9.16 by Tatsuro
> octave:2> ts=cputime();
> octave:3> for n=1:1000;1==1;end;
> octave:4> cputime()-ts
> ans =  0.11000        
> 
> MSVC octave-2.9.15 by Michael
> octave:4> ts=cputime();
> octave:5> for n=1:1000;1==1;end;
> octave:6> cputime()-ts
> ans =  0.12500
 
> For the cygwin octave-2.9.16 and MSVC octave-2.9.16, the cputime is correct.  
> This bug seems to be imported when the octave was upgraded to 2.9.16 only for 
> native windows
> version.
> 
> Tatsuro
> 
> 
> --------------------------------------
> New Design Yahoo! JAPAN  2008/01/01
> http://pr.mail.yahoo.co.jp/newdesign/
> 


--------------------------------------
New Design Yahoo! JAPAN  2008/01/01
http://pr.mail.yahoo.co.jp/newdesign/