[Boost-commit] svn:boost r81870 - in trunk: boost/functional/hash libs/functional/hash/doc

Subject: [Boost-commit] svn:boost r81870 - in trunk: boost/functional/hash libs/functional/hash/doc
From: dnljms_at_[hidden]
Date: 2012-12-12 04:44:34

Author: danieljames
Date: 2012-12-12 04:44:32 EST (Wed, 12 Dec 2012)
New Revision: 81870
URL: http://svn.boost.org/trac/boost/changeset/81870

Log:
Hash: Fix int128 with BOOST_HASH_NO_EXTENSIONS.

I don't think int128 should count as an extension.

BOOST_HASH_NO_EXTENSIONS is actually a bit of a pain, and I don't think it's
that useful. Maybe I should deprecate it.
Text files modified: 
   trunk/boost/functional/hash/hash.hpp       |     5 +++++                                   
   trunk/libs/functional/hash/doc/changes.qbk |     3 +++                                     
   2 files changed, 8 insertions(+), 0 deletions(-)

Modified: trunk/boost/functional/hash/hash.hpp
==============================================================================
--- trunk/boost/functional/hash/hash.hpp	(original)
+++ trunk/boost/functional/hash/hash.hpp	2012-12-12 04:44:32 EST (Wed, 12 Dec 2012)
@@ -439,6 +439,11 @@
     BOOST_HASH_SPECIALIZE(boost::ulong_long_type)
 #endif
 
+#if defined(BOOST_HAS_INT128)
+    BOOST_HASH_SPECIALIZE(boost::int128_type)
+    BOOST_HASH_SPECIALIZE(boost::uint128_type)
+#endif
+
 #if !defined(BOOST_NO_CXX11_HDR_TYPEINDEX)
     BOOST_HASH_SPECIALIZE(std::type_index)
 #endif

Modified: trunk/libs/functional/hash/doc/changes.qbk
==============================================================================
--- trunk/libs/functional/hash/doc/changes.qbk	(original)
+++ trunk/libs/functional/hash/doc/changes.qbk	2012-12-12 04:44:32 EST (Wed, 12 Dec 2012)
@@ -142,6 +142,9 @@
 [h2 Boost 1.52.0]
 
 * Restore `enum` support, which was accidentally removed in the last version.
+* Add support for `boost::int128_type` and `boost::uint128_type` where
+  available - currently only `__int128` and `unsigned __int128` on some
+  versions of gcc.
 * New floating point hasher - will hash the binary representation on more
   platforms, which should be faster.
 * On platforms that are known to have standard floating point, don't use the