explicit-failures-markup.xml 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  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&lt;T[N]&gt;, boost::hash_combine and boost::hash_range
  19. work.
  20. </note>
  21. </mark-expected-failures>
  22. <mark-expected-failures>
  23. <test name="hash_function_pointer_test"/>
  24. <toolset name="msvc-6.5*"/>
  25. <toolset name="msvc-7.0*"/>
  26. <note refid="2" author="Daniel James"/>
  27. </mark-expected-failures>
  28. <mark-expected-failures>
  29. <test name="hash_function_pointer_test"/>
  30. <toolset name="sun-5.7"/>
  31. <toolset name="sun-5.8"/>
  32. <toolset name="sun-5.9"/>
  33. <note author="Daniel James">
  34. On these compilers the wrong overload of hash_value is called
  35. when the argument is a hash function pointer. So calling
  36. hash_value doesn't work but boost::hash does work (and it's
  37. recommended that user never call hash_value directly so this
  38. shouldn't be a problem).
  39. </note>
  40. </mark-expected-failures>
  41. <mark-expected-failures>
  42. <test name="hash_long_double_test"/>
  43. <toolset name="gcc-3.4.3_sunos"/>
  44. <toolset name="*pa_risc"/>
  45. <note author="Daniel James">
  46. This platform has poor support for <code>long double</code> so
  47. the hash function perform poorly for values out of the range
  48. of <code>double</code> or if they differ at a greater precision
  49. that <code>double</code> is capable of representing.
  50. </note>
  51. </mark-expected-failures>
  52. <mark-expected-failures>
  53. <test name="point" />
  54. <test name="books" />
  55. <toolset name="msvc-6.5*"/>
  56. <toolset name="msvc-7.0*"/>
  57. <note author="Daniel James">
  58. These examples only work on compilers with support for ADL.
  59. It is possible to work around this, but I wanted to keep the
  60. example code as clean as possible.
  61. </note>
  62. </mark-expected-failures>
  63. <mark-expected-failures>
  64. <test name="point" />
  65. <toolset name="borland-*"/>
  66. <note author="Daniel James">
  67. It appears that Borland doesn't find friend functions defined
  68. in a class by ADL. This is easily fixed but this example is
  69. meant to show the typical way of customising boost::hash, not
  70. the portable way.
  71. </note>
  72. </mark-expected-failures>
  73. <mark-expected-failures>
  74. <test name="hash_global_namespace_test" />
  75. <toolset name="borland-*"/>
  76. <note author="Daniel James">
  77. The test demonstrates a Borland bug - functions that aren't
  78. in a namespace don't appear to be found by ADL.
  79. </note>
  80. </mark-expected-failures>
  81. <mark-expected-failures>
  82. <test name="container_fwd_gcc_debug"/>
  83. <toolset name="darwin-4.2"/>
  84. <note author="Daniel James">
  85. Debug containers aren't supported on Apple's version of gcc 4.2.
  86. </note>
  87. </mark-expected-failures>
  88. </library>
  89. </explicit-failures-markup>