Openlibm: Difference between revisions

Jump to navigation Jump to search
1,150 bytes added ,  28 July 2022
no edit summary
No edit summary
No edit summary
Line 82: Line 82:
    
    
   (inf,nan), (inf,nan), (-inf,inf), (inf,nan)
   (inf,nan), (inf,nan), (-inf,inf), (inf,nan)
*;''Observations :''
The expected output is not achieved by compiling the program with Openlibm. Also, the output is not consistent with systems and different compilers. Hence, the openlibm as a proposed solution to solve this bug has failed.


===Testing of bug {{bug|62212}}===
===Testing of bug {{bug|62212}}===
Line 118: Line 121:
   db_large_integer: 1.84467e+19
   db_large_integer: 1.84467e+19
   ui64_large_integer: 0
   ui64_large_integer: 0
*;''Observations:''
On Ubuntu, openlibm failed to link when compiling. The expected output is not achieved by compiling the program with Openlibm. Even compiling with OpenLibm is not giving any difference to the output. Hence, the openlibm as a proposed solution to solve this bug has failed.


===Testing of bug {{bug|62332}}===
===Testing of bug {{bug|62332}}===
Line 210: Line 215:
     0.707107+1e-57i-->0.785398+-0i
     0.707107+1e-57i-->0.785398+-0i
     0.707107+1e-60i-->0.785398+-0i
     0.707107+1e-60i-->0.785398+-0i
*;''Observations: ''
Compiling with the Openlibm is providing the output that we want to avoid. The expected output is not achieved by compiling the program with Openlibm. Hence, the openlibm as a proposed solution to solve this bug has failed.
                      
                      
    
    
 
==Conclusion==
 
The proposed solution is to use Openlibm as a replacement of libm to deal with the inconsistency in the maths library caused when Octave is compiled with libc++ (default on macOS) and sometimes with libstdc++ has failed and the bug issues and can not be solved with openlibm. Hence, there is a need to find an alternate solution to address this issue.
 






[[Category:Development]]
[[Category:Development]]

Navigation menu