1<?xml version="1.0" encoding="utf-8"?> 2<!-- 3 Copyright 2018 Daniel James 4 Distributed under the Boost Software License, Version 1.0. 5 (See accompanying file LICENSE_1_0.txt or copy at 6 http://www.boost.org/LICENSE_1_0.txt) 7--> 8<explicit-failures-markup> 9 <!-- container_hash --> 10 <library name="container_hash"> 11 <mark-expected-failures> 12 <test name="hash_value_array_test"/> 13 <toolset name="msvc-6.5*"/> 14 <toolset name="msvc-7.0*"/> 15 <note author="Daniel James"> 16 hash_value is not overloaded for arrays for older versions 17 of Visual C++. There is a work around so that 18 boost::hash<T[N]>, boost::hash_combine and boost::hash_range 19 work. 20 </note> 21 </mark-expected-failures> 22 23 <mark-expected-failures> 24 <test name="hash_function_pointer_test"/> 25 <toolset name="msvc-6.5*"/> 26 <toolset name="msvc-7.0*"/> 27 <note refid="2" author="Daniel James"/> 28 </mark-expected-failures> 29 30 <mark-expected-failures> 31 <test name="hash_function_pointer_test"/> 32 <toolset name="sun-5.7"/> 33 <toolset name="sun-5.8"/> 34 <toolset name="sun-5.9"/> 35 <note author="Daniel James"> 36 On these compilers the wrong overload of hash_value is called 37 when the argument is a hash function pointer. So calling 38 hash_value doesn't work but boost::hash does work (and it's 39 recommended that user never call hash_value directly so this 40 shouldn't be a problem). 41 </note> 42 </mark-expected-failures> 43 44 <mark-expected-failures> 45 <test name="hash_long_double_test"/> 46 <toolset name="gcc-3.4.3_sunos"/> 47 <toolset name="*pa_risc"/> 48 <note author="Daniel James"> 49 This platform has poor support for <code>long double</code> so 50 the hash function perform poorly for values out of the range 51 of <code>double</code> or if they differ at a greater precision 52 that <code>double</code> is capable of representing. 53 </note> 54 </mark-expected-failures> 55 56 <mark-expected-failures> 57 <test name="point" /> 58 <test name="books" /> 59 <toolset name="msvc-6.5*"/> 60 <toolset name="msvc-7.0*"/> 61 <note author="Daniel James"> 62 These examples only work on compilers with support for ADL. 63 It is possible to work around this, but I wanted to keep the 64 example code as clean as possible. 65 </note> 66 </mark-expected-failures> 67 68 <mark-expected-failures> 69 <test name="point" /> 70 <toolset name="borland-*"/> 71 <note author="Daniel James"> 72 It appears that Borland doesn't find friend functions defined 73 in a class by ADL. This is easily fixed but this example is 74 meant to show the typical way of customising boost::hash, not 75 the portable way. 76 </note> 77 </mark-expected-failures> 78 79 <mark-expected-failures> 80 <test name="hash_global_namespace_test" /> 81 <toolset name="borland-*"/> 82 <note author="Daniel James"> 83 The test demonstrates a Borland bug - functions that aren't 84 in a namespace don't appear to be found by ADL. 85 </note> 86 </mark-expected-failures> 87 88 <mark-expected-failures> 89 <test name="container_fwd_gcc_debug"/> 90 <toolset name="darwin-4.2"/> 91 <note author="Daniel James"> 92 Debug containers aren't supported on Apple's version of gcc 4.2. 93 </note> 94 </mark-expected-failures> 95 </library> 96</explicit-failures-markup> 97