Re: [Fwd: [Bug c++/14563] octave built under Cygwin very slow]

[Paul Thomas]

Paul Kienzle wrote:

> Octave's signal handlers set a flag saying that octave should quit.  The
> OCTAVE_QUIT  macro tests this flag and throws an exception.  For your
> needs you don't need to handle Ctrl-C, so skip it:

Paul,

Thank you for a rather complete breakdown of how to disable the signal 
and error handling.  I realise from reading the list just after 
octave-2.1.39 how much you contributed to the design.  It is also a 
salutory lesson in how much I have to learn!

Before engaging in the gritty business of disabling the signal and error 
handling, I thought that I would try jwe's suggestion of building 
octave-2.1.39.  The results are, I think, a bit of a setback:

Under the same Cygwin, on the same machine and in the same sitting, using

tic ; tot = 0 ; x = [ 1:1e5 ] ; for i = 1:1e5 ; tot = tot + x(i) ; end ; 
toc

I found

gcc-3.2    20020927 (prerelease)           octave-2.1.56 (PK special)   
1.51 seconds
gcc-3.3.1  (cygming special)                 octave-2.1.50               
      11.97 seconds
          ditto                                           
octave-2.1.39                      12.75 seconds

The time for the octave-2.1.56 is typical for any of the octave versions 
that have been built with gcc-3.2.

Does this defintively takd error and signal handling out of the firing line?

BTW fsolve had to have a bit of Band-Aid applied before it would build - 
it was missing one or two backslashes.

Paul T