|
From: | Paul Thomas |
Subject: | Re: Packaging Octave for Windows and OS X (was: writing integer with fwrite) |
Date: | Tue, 14 Dec 2004 18:55:10 +0100 |
Dear All,
My understanding is that this is due to the way exception handling is implemented in GCC 3.3 for Cygwin. Does anyone know whether this is likely to improve any time soon? Long term, we need to support improving the compiler.
I am still in sporadic communication with the gcc developers about this.I had an attempt at building octave with gcc-4.0.0 somewhile back. It bombed out because of clashes between the new fortran library and libm, amongst others. I left it at that point, thinking that this is something that will get straightened out in time. I therefore did not push on to test build the c++ libraries. It was something of a surprise, therefore, when I repeated some of the new/delete tests with g++-4.0.0 and found that the slowness has gone away. Nobody has explained it yet but I suspect that I am getting dwarf2 as a default, rather than -sjlj. It might, therefore be worth either fixing the libgfortran/libm clashes or using g77-3.4.x, instead of gfortran.
Paul T
------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------
[Prev in Thread] | Current Thread | [Next in Thread] |