From 7911f491f6fabac85121acbdb8e1ea1e379e2df3 Mon Sep 17 00:00:00 2001 From: Daniel James Date: Wed, 3 May 2017 04:21:52 +0100 Subject: [PATCH] Try using own allocator_traits with Sun compiler The good news is that the old Sun workarounds aren't needed any more. Unfortunately, there are a lot of exception test errors for unordered_map and unordered_multimap when using libstdc++, which probably means that std::pair isn't exception safe, which is a bit odd. But first try using our allocator_traits implementation instead of the standard one to see if that makes a difference. If it doesn't then I'll probably just disable C++11 construction on this compiler, which should fix the problem but will make allocators less useful. --- include/boost/unordered/detail/implementation.hpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/boost/unordered/detail/implementation.hpp b/include/boost/unordered/detail/implementation.hpp index 49bc321e..d436613b 100644 --- a/include/boost/unordered/detail/implementation.hpp +++ b/include/boost/unordered/detail/implementation.hpp @@ -75,7 +75,7 @@ // 2 = boost::container::allocator_traits #if !defined(BOOST_UNORDERED_USE_ALLOCATOR_TRAITS) -#if !defined(BOOST_NO_CXX11_ALLOCATOR) +#if !defined(BOOST_NO_CXX11_ALLOCATOR) && !BOOST_COMP_SUNPRO #define BOOST_UNORDERED_USE_ALLOCATOR_TRAITS 1 #elif defined(BOOST_MSVC) #if BOOST_MSVC < 1400