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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture not specified
Severity High
Priority Urgent
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 30%
Votes 0
Private No

Details

octave 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).
This task depends upon
 FS#2214 - gcc-g77 not available in repos 

This task blocks these from closing
 FS#2213 - [octave 2.1.64-1] basic computations fail 
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.
Comment by Damir Perisa (damir.perisa) - Friday, 28 January 2005, 13:11 GMT
FFLAGS="-O2 -ffloat-store ... i'll check that

Loading...