From maintainers-request at octave dot org Fri Nov 19 13:40:53 2004 Subject: Re: How to make Octave build and run natively on Windows? From: "John W. Eaton" To: "Laurent Mazet" Cc: , "Ole Jacob Hagen" , "David Bateman" , "Laurent Mazet" Date: Fri, 19 Nov 2004 14:41:00 -0500 On 19-Nov-2004, Laurent Mazet wrote: | As sugested Ole, I run the Octave2 test from | http://www.sciviews.org/other/benchmark.htm on my MinGW Octave to evaluate If I'm looking at the same benchmark that you used, then it uses tic and toc for timing, which is not reliable because it measures wall-clock time and that can be affected by other processes running on your system when you run the tests. | By the way, I realized that the kpathsearch doesn't work properly and I | have to source all the used functions: | %%%% Shell function | %% function get () { | %% f="$1".m; find /usr/local/share/octave/2.1.60/m/ -name $f -exec cp {} | \; | %% sed 's/\(libs={\)/\1"'$1'"; /' Octave2.m >t | %% mv -f t Octave2.m | %% } | libs={"trace"; "cov"; "corrcoef"; "gcd2"; "strcmp"; "mean"; "rem"; | "is_leap_year"; "isvector"; "etime"; "clock"; "toc"; "tic"; "findstr"; | "split"; "rows"; "setstr"; "isscalar"; "columns"; "repmat"; "deblank"; | "strcat"; "isstr"; "num2str"}; | for n=1:length(libs); | source([libs{n}, ".m"]); | endfor Can you investigate what might be causing this? There is extensive tracing code in the path searching functions that you can enable. | On the same computer, I run the standard Octave2.m test on octave 2.1.50a | from http://octave.sf.net i.e. with octave-forge and a blas optimzed for | PIII (some segfault on my Duron :-( ): If the BLAS is optimized for PIII, then couldn't that be the reason that you are seeing different results rather than it being linked with Cygwin? It seems to me that we need a comparison where the only difference is Cygwin vs. no Cygwin. jwe