Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2060 - octave produces wrong results because of over optimization
Attached to Project:
Arch Linux
Opened by Askadar (askadar) - Monday, 24 January 2005, 18:48 GMT
Last edited by Damir Perisa (damir.perisa) - Friday, 28 January 2005, 13:12 GMT
Opened by Askadar (askadar) - Monday, 24 January 2005, 18:48 GMT
Last edited by Damir Perisa (damir.perisa) - Friday, 28 January 2005, 13:12 GMT
|
Detailsoctave has a problem when compiled with gcc > 3.3. Some alogrithms do not work correctly because of a floating point optimization by the compiler.
Details: http://www.octave.org/octave-lists/archive/help-octave.2004/msg02638.html Solution: Recompile octave with new FFLAGS (see link). |
Closed by Jan de Groot (JGC)
Wednesday, 23 February 2005, 11:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed by compiling with gcc-g77 and setting FFLAGS.
Wednesday, 23 February 2005, 11:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed by compiling with gcc-g77 and setting FFLAGS.
Comment by Damir Perisa (damir.perisa) -
Friday, 28 January 2005, 13:11 GMT
FFLAGS="-O2 -ffloat-store ... i'll check that