summaryrefslogtreecommitdiff
path: root/integer.cpp
diff options
context:
space:
mode:
authorJeffrey Walton <noloader@gmail.com>2018-08-22 14:46:30 -0400
committerJeffrey Walton <noloader@gmail.com>2018-08-22 14:46:30 -0400
commit0ba3687c3957ee33d040e3fa38ea84d6fd8b819e (patch)
tree17c9a8b2e2b0429cdaebc59f2ffc964512149a24 /integer.cpp
parentaf17fdf91b3ac6cb90ebd9fc41a89e1fb5be7546 (diff)
downloadcryptopp-git-0ba3687c3957ee33d040e3fa38ea84d6fd8b819e.tar.gz
Update comments
Diffstat (limited to 'integer.cpp')
-rw-r--r--integer.cpp12
1 files changed, 5 insertions, 7 deletions
diff --git a/integer.cpp b/integer.cpp
index 842175ad..2d7f41dc 100644
--- a/integer.cpp
+++ b/integer.cpp
@@ -105,13 +105,11 @@ NAMESPACE_BEGIN(CryptoPP)
// Function body near the middle of the file
static void SetFunctionPointers();
-// We used to jump through some hoops to set the function pointers once,
-// including std::call_once. Later we learned std::call_once was fairly
-// buggy due to interactions between libstdc++, glibc and pthreads.
-// Now we use a double-checked pattern. We are not leaking anything so
-// it does not matter if a pointer is written twice during a race.
-// Also see GCC Issue 66146, "call_once not C++11-compliant" (on many
-// platforms), http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66146 and
+// Use a double-checked pattern. We are not leaking anything so it
+// does not matter if a pointer is written twice during a race.
+// Avoid std::call_once due to too many problems on platforms like
+// Solaris and Sparc. Also see
+// http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66146 and
// http://github.com/weidai11/cryptopp/issues/707.
InitializeInteger::InitializeInteger()
{