sc/source/core/opencl/opinlinefun_statistical.cxx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e3c8de29dd9e947599a8f8991c1597b8fe263d1a
Author: Mike Kaganski <mike.kagan...@collabora.com>
AuthorDate: Fri Nov 19 00:22:31 2021 +0300
Commit: Mike Kaganski <mike.kagan...@collabora.com>
CommitDate: Fri Nov 19 17:40:41 2021 +0100
Use more precise value for M_PI in OpenCL
No idea if that would make actual difference, but it simply looks
odd that we use such a value, in view of all other efforts to improve
accuracy of rad<->deg conversions.
The value is used that is already present elsewhere in the code, e.g.
in sc/source/core/opencl/op_statistical.cxx.
Change-Id: I098f2bf748670e3250035d74d1bf7d1e224dd66b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/125557
Tested-by: Jenkins
Reviewed-by: Mike Kaganski <mike.kagan...@collabora.com>
diff --git a/sc/source/core/opencl/opinlinefun_statistical.cxx
b/sc/source/core/opencl/opinlinefun_statistical.cxx
index 6988ff7f03e8..f981345df96d 100644
--- a/sc/source/core/opencl/opinlinefun_statistical.cxx
+++ b/sc/source/core/opencl/opinlinefun_statistical.cxx
@@ -10,7 +10,7 @@
#ifndef SC_OPENCL_OPINLINFUN_statistical
#define SC_OPENCL_OPINLINFUN_statistical
std::string MinDecl = "#define Min 2.22507e-308\n";
-std::string F_PIDecl="#define M_PI 3.1415926\n";
+std::string F_PIDecl="#define M_PI 3.1415926535897932384626433832795\n";
std::string fBigInvDecl ="#define fBigInv 2.22045e-016\n";
std::string fMachEpsDecl ="#define fMachEps 2.22045e-016\n";
std::string fLogDblMaxDecl ="#define fLogDblMax log(1.79769e+308)\n";
