Openlibm: Difference between revisions

Jump to navigation Jump to search
532 bytes added ,  28 July 2022
m
No edit summary
Line 72: Line 72:
}
}
</syntaxhighlight>
</syntaxhighlight>


*;Output Expected :  
*;Output Expected :  
Line 108: Line 107:
*;''Observations :''  
*;''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.
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}} ===
*;CODE SOURCE: [https://github.com/shreyaswikriti/BugTesting/blob/main/bug%2362212.cc C++ PROGRAM]
 
*;CODE SOURCE:
 
<syntaxhighlight lang="C++">
#include <cmath>
#include <iostream>
 
int main (void)
{
  double db_large_integer = std::pow (2., 64.);
  std::cout << "db_large_integer: " << db_large_integer << std::endl;
  uint64_t ui64_large_integer = db_large_integer;
  std::cout << "ui64_large_integer: " << ui64_large_integer << std::endl;
  return 0;
}
</syntaxhighlight>


*;Output Expected :  
*;Output Expected :  
Line 148: Line 162:
  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.
  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}} ===
*;CODE SOURCE: [https://github.com/shreyaswikriti/BugTesting/blob/main/bug%2362332.cc C++ PROGRAM]
 
*;CODE SOURCE:
 
<syntaxhighlight lang="C++">
#include <iostream>
#include <cmath>
#include <complex>
#define cosd(x) (cos((x) * M_PI / 180))
int main()
{
    for(int i=1;i<=20;i++)
    { std::complex<double> x( cosd(45) , std::pow(10, -3*i) );
    std::cout << real(x)<<"+"<<imag(x)<<"i"<<"-->"<<real(acos(x))<<"+"<<imag(acos(x))<<"i"<< std::endl ;}
}
</syntaxhighlight>


*;Output Expected :  
*;Output Expected :  
Line 239: Line 267:
     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: ''
*;''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.
 
                   
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==
==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.
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.

Navigation menu