Pārlūkot izejas kodu

Merging fixes to release; fixes #2294 fixes #4918 fixes #3645 refs #2823 refs #1427 refs #2893

[SVN r67792]
Marshall Clow 15 gadi atpakaļ
vecāks
revīzija
bf8abeebda
4 mainītis faili ar 146 papildinājumiem un 59 dzēšanām
  1. 1 1
      libs/concept_check
  2. 1 1
      libs/fusion
  3. 1 1
      libs/iterator
  4. 143 56
      status/explicit-failures-markup.xml

+ 1 - 1
libs/concept_check

@@ -1 +1 @@
-Subproject commit 807fcd7b9723c5945009e69a82c1f286a6c6dbff
+Subproject commit 7dec68923ddf03a9ab8e90d7648051229a02fc70

+ 1 - 1
libs/fusion

@@ -1 +1 @@
-Subproject commit cd811f56bcceb97bdc01cb992d2d7f40b7958ac6
+Subproject commit 94f5406936ab6ddebe42608fc30f995f6e9ad078

+ 1 - 1
libs/iterator

@@ -1 +1 @@
-Subproject commit de4ef14f9bc3754a415c2a506713e32187abb313
+Subproject commit 36565eae6360dbd57bf70c235ddc1378e802e61d

+ 143 - 56
status/explicit-failures-markup.xml

@@ -478,6 +478,17 @@
         </test>
     </library>
 
+    <!-- chrono -->
+    <library name="chrono">
+      <mark-unusable>
+        <toolset name="borland-*"/>
+        <toolset name="pathscale*"/>
+        <note author="Vicente J. Botet Escriba">
+            The compiler does not support features that are essential for the library.
+        </note>
+      </mark-unusable>
+    </library>
+
     <!-- circular_buffer -->
     <library name="circular_buffer">
         <mark-expected-failures>
@@ -619,7 +630,7 @@
                 <toolset name="msvc-7.1*"/>
                 <toolset name="acc"/>
                 <note author="Alexander Nasonov">
-                    Conversion double-string-double may give a different value (or even throw) on many compilers 
+                    Conversion double-string-double may give a different value (or even throw) on many compilers
                 </note>
             </mark-failure>
         </test>
@@ -1394,7 +1405,7 @@
           <toolset name="sun-5.7"/>
           <toolset name="sun-5.8"/>
           <note author="Beman Dawes">
-              The library works well with versions of this compiler 5.9 and later 
+              The library works well with versions of this compiler 5.9 and later
           </note>
         </mark-expected-failures>
         <mark-expected-failures>
@@ -1820,7 +1831,7 @@
             <toolset name="acc"/>
             <note author="Tobias Schwinger">
                 Those failures are due to not quite const-correct overload
-                resolution. The complaints from the test suite should rarely 
+                resolution. The complaints from the test suite should rarely
                 matter in practice - the corresponding components are basically
                 usable. With aCC6, when compiled in strict ansi mode, the test
                 succeeds.
@@ -1847,37 +1858,15 @@
         <mark-unusable>
             <toolset name="borland-5.*"/>
             <toolset name="borland-6.*"/>
-            <!-- Open64 and Pathscale ICE on almost all test cases, often
-            because of http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17327;
-            property type detection fails because it uses enum types as tags.
-            -->
-            <toolset name="gcc-open64"/>
-            <toolset name="pathscale-3.1"/>
-            <!-- vacpp ICEs on many of the tests -->
-            <toolset name="vacpp"/>
+            <toolset name="borland-cb2009"/>
+            <toolset name="borland-cb2010"/>
+            <toolset name="sun-5.9"/>
         </mark-unusable>
         <mark-expected-failures>
-          <test name="graphviz_test"/>
-          <toolset name="vc-8_0"/>
-          <toolset name="msvc-8_0"/>
-          <toolset name="intel-vc71-win-9.1"/>
-          <note refid="1" author="Doug Gregor"/>
-        </mark-expected-failures>
-        <mark-expected-failures>
-          <test name="graphviz_test"/>
-          <toolset name="como-4_3_3-vc7_1"/>
-          <note refid="3" author="Doug Gregor"/>
-        </mark-expected-failures>
-        <mark-expected-failures>
-            <test name="bundled_properties"/>
-            <toolset name="qcc-3.3*"/>
-            <note author="Jim Douglas" date="18 Feb 06" refid="27"/>
-        </mark-expected-failures>
-        <mark-expected-failures>
-          <test name="boykov_kolmogorov_max_flow_test"/>
-          <test name="max_flow_test"/>
-          <toolset name="acc*"/>
-          <note author="Markus Schoepflin" refid="45"/>
+          <test name="grid_graph_cc"/>
+          <test name="grid_graph_test"/>
+          <toolset name="msvc-7.1"/>
+          <note author="Jeremiah Willcock" refid="2"/>
         </mark-expected-failures>
     </library>
 
@@ -1891,7 +1880,7 @@
                 When compiling with aC++, depending on system load, the compile time may exceed
                 specified timeout value. The test passes when the timeout value is increased.
                 When compiling with GCC, linker takes segmentation fault.
-                In the HP bug tracking system, this issue is tracked as QuIX ID: QXCR1000836120.  
+                In the HP bug tracking system, this issue is tracked as QuIX ID: QXCR1000836120.
             </note>
         </mark-expected-failures>
     </library>
@@ -1912,7 +1901,6 @@
             <toolset name="mipspro"/>
             <toolset name="acc*"/>
             <toolset name="msvc-8.0~wm5*"/>
-            <toolset name="vacpp*"/>
             <toolset name="pathscale*"/>
             <toolset name="intel-linux-8.*"/>
             <toolset name="gcc-3.4.6_linux_ia64"/>
@@ -1934,7 +1922,6 @@
             <toolset name="gcc-3.2*"/>
             <toolset name="gcc-3.3*"/>
             <toolset name="mipspro"/>
-            <toolset name="vacpp*"/>
             <toolset name="pathscale*"/>
             <toolset name="intel-linux-8.*"/>
             <note author="Ion Gazta&#241;aga">
@@ -2139,7 +2126,7 @@
             <toolset name="vacpp"/>
             <note author="Jonathan Turkanis" date="06 Jan 2008">
                 "restrict" is treated as a keyword on this platform (as in C99);
-                use the alias "slice" instead, defined in 
+                use the alias "slice" instead, defined in
                 "boost/iostreams/slice.hpp."
             </note>
         </mark-expected-failures>
@@ -2163,8 +2150,8 @@
             <test name="stream_offset_64bit_test"/>
             <toolset name="borland-*"/>
             <note author="Jonathan Turkanis" date="04 Jan 2008">
-                In the Dinkumware standard library, streampos relies on fpos_t 
-                to store stream offsets, but fpos_t is defined as a 32-bit 
+                In the Dinkumware standard library, streampos relies on fpos_t
+                to store stream offsets, but fpos_t is defined as a 32-bit
                 long by the Borland runtime library. In Borland's modified
                 version of STLPort, streampos relies on streamoff to store
                 stream offsets, but streamoff is defined to be a 32-bit long.
@@ -2182,8 +2169,8 @@
             <test name="stream_offset_64bit_test"/>
             <toolset name="vacpp*"/>
             <note author="Jonathan Turkanis" date="09 Jan 2008">
-                On this platform, streampos is an alias for fpos, whose 
-                implementation stores stream offsets using streamsize and 
+                On this platform, streampos is an alias for fpos, whose
+                implementation stores stream offsets using streamsize and
                 fpos_t; both of the latter types are 32-bit
             </note>
         </mark-expected-failures>
@@ -2204,8 +2191,8 @@
             <test name="stream_offset_64bit_test"/>
             <toolset name="gcc-4.2"/>
             <note author="Jonathan Turkanis" date="09 Jan 2008">
-              The following applies only to gcc-4.2 using the stdcxx 
-              standard library: On this platform, streampos is an alias for 
+              The following applies only to gcc-4.2 using the stdcxx
+              standard library: On this platform, streampos is an alias for
               ptrdiff_t, which is an alias for a 32-bit type
             </note>
         </mark-expected-failures>
@@ -2559,24 +2546,52 @@ for more information.
             <toolset name="gcc-3.4.6_linux_ia64"/>
             <toolset name="gcc-4.2.*"/>
             <toolset name="gcc-4.1.2_sunos_i86pc"/>
-                <note author="Fernando Cacciola" refid="2"/>
+                <note author="Fernando Cacciola" id="optional-compiler-bug">
+                <p>This failure is caused by a compiler bug, and as far as we can 
+                tell, can't be worked around in the library, although we think 
+                the library might be made safer with respect to this bug.</p>
+
+                <p>Specifics: the following simple test fails when it should succeed.</p>
+                <pre>
+                #include &lt;cassert&gt;
+
+                int const x = 0;
+                struct A
+                {
+                   A(int const&amp; y)
+                   {
+                     assert(&amp;x == &amp;y);
+                   }
+                };
+
+                int main()
+                {
+                    A a(x);  // direct initialization works fine
+                    A b = x; // copy initialization causes x to be copied before it is bound
+                }
+                </pre>
+
+                The possible safety enhancement would be to cause the constructor 
+                in question to be explicit for optional&lt;T const&amp;&gt;; that 
+                would prevent copy initialization.
+                </note>
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="optional_test_ref_fail1"/>
             <toolset name="borland-5.6*"/>
             <toolset name="borland-5.8*"/>
             <toolset name="borland-5.9*"/>
-            <note author="Fernando Cacciola" refid="2"/>
+            <note author="Fernando Cacciola" refid="optional-compiler-bug"/>
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="optional_test_fail3a"/>
             <toolset name="gcc-3_3-darwin"/>
-            <note author="Fernando Cacciola" refid="2"/>
+            <note author="Fernando Cacciola" refid="optional-compiler-bug"/>
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="optional_test_inplace_fail2"/>
             <toolset name="gcc-3_3-darwin"/>
-            <note author="Fernando Cacciola" refid="2"/>
+            <note author="Fernando Cacciola" refid="optional-compiler-bug"/>
         </mark-expected-failures>
     </library>
 
@@ -2845,6 +2860,13 @@ for more information.
             <toolset name="*"/>
             <note refid="40" author="Boris Gubenko"/>
         </mark-expected-failures>
+        <mark-expected-failures>
+            <test name="sp_convertible_test"/>
+            <test name="wp_convertible_test"/>
+            <test name="ip_convertible_test"/>
+            <toolset name="borland-*"/>
+            <note refid="31" author="Peter Dimov"/>
+        </mark-expected-failures>
    </library>
 
     <!-- spirit -->
@@ -4131,8 +4153,8 @@ for more information.
             <toolset name="pathscale-3.1"/>
             <toolset name="sun-5.*"/>
             <note author="Thorsten Ottosen">
-                For codewarrior, the cause of this problem is unknown. Please 
-                submit a patch. Other failures are due to problems with 
+                For codewarrior, the cause of this problem is unknown. Please
+                submit a patch. Other failures are due to problems with
                 the serialization library, or to a minor problem with the use of
                 the library.
             </note>
@@ -4346,6 +4368,7 @@ for more information.
     <!-- range -->
     <library name="range">
         <mark-unusable>
+            <toolset name="borland-*"/>
             <toolset name="mipspro"/>
             <toolset name="dmc-8_43-stlport-4_5_3"/>
             <toolset name="gcc-2.95.3*"/>
@@ -4360,6 +4383,15 @@ for more information.
             <toolset name="borland-5.9*"/>
             <note refid="27" author="Thorsten Ottosen"/>
         </mark-expected-failures>
+        <mark-expected-failures>
+            <test name="adl_conformance"/>
+            <toolset name="msvc-7.1"/>
+            <note author="Neil Groves">
+                This test is designed to give users visibility of the ADL problems with their compilers.
+                Lack of Argument Dependent Lookup changes how one can extend the library. The lack of
+                ADL is worked-around internally so that most of the functionality is preserved.
+            </note>
+        </mark-expected-failures>
         <mark-expected-failures>
             <test name="iterator_range"/>
             <toolset name="msvc-stlport"/>
@@ -4374,6 +4406,14 @@ for more information.
                 For other compilers it is simply a bug in the standard library.
             </note>
         </mark-expected-failures>
+        <mark-expected-failures>
+            <test name="push_front"/>
+            <toolset name="msvc-9.0~stlport5.2"/>
+            <note author="Neil Groves">
+                push_front fails the unit test in this configuration. I do not have this
+                configuration available to determine if a work-around is possible.
+            </note>
+        </mark-expected-failures>
         <mark-expected-failures>
             <test name="reversible_range"/>
             <toolset name="hp_cxx-65*"/>
@@ -4431,6 +4471,29 @@ for more information.
         </mark-expected-failures>
     </library>
 
+    <!-- ratio -->
+    <library name="ratio">
+      <mark-unusable>
+        <toolset name="borland-*"/>
+        <toolset name="pathscale*"/>
+        <note author="Vicente J. Botet Escriba">
+            The compiler does not support features that are essential for the library.
+        </note>
+      </mark-unusable>
+        <mark-expected-failures>
+            <test name="mpl_plus_pass"/>
+            <test name="ratio_ext_pass"/>
+            <toolset name="intel-*-10.1"/>
+            <toolset name="intel-*-11.0"/>
+            <toolset name="intel-*-11.1"/>
+            <note author="Vicente J. Botet Escriba">
+                internal error: assertion failed: copy_template_param_expr.
+                It seems to be already an Intel internal bug database (tracker number #82149).
+                I have no workaround yet.
+            </note>
+        </mark-expected-failures>
+    </library>
+
     <!-- regex -->
     <library name="regex">
         <test name="regex_token_iterator_eg_2">
@@ -4484,7 +4547,7 @@ for more information.
           <toolset name="darwin*"/>
           <note author="J. Maddock">
              This tests fails because a dependency (Boost.Test)
-             fails to initialise correctly.  The issue has been 
+             fails to initialise correctly.  The issue has been
              reported to the library's author.
           </note>
        </mark-expected-failures>
@@ -4648,9 +4711,16 @@ for more information.
 
     <!-- statechart -->
     <library name="statechart">
+        <mark-unusable>
+            <toolset name="borland*"/>
+            <toolset name="sun-5*"/>
+            <toolset name="pgi-1*"/>
+            <note author="Andreas Huber" refid="17"/>
+        </mark-unusable>
         <mark-expected-failures>
             <test name="DllTestNormal"/>
             <toolset name="*mingw*"/>
+            <toolset name="intel-darwin-10*"/>
             <toolset name="intel-darwin-11*"/>
             <note author="Andreas Huber">
                 A runtime failure of this test indicates that this platform
@@ -4663,11 +4733,13 @@ for more information.
         </mark-expected-failures>
         <mark-expected-failures reason="?">
             <test name="FifoSchedulerTest*"/>
-            <toolset name="intel-darwin-11*"/>
+            <toolset name="darwin-4.4"/>
+            <toolset name="intel-darwin-10*"/>
             <note author="Andreas Huber" refid="29"/>
         </mark-expected-failures>
         <mark-expected-failures reason="?">
             <test name="TransitionTest*"/>
+            <toolset name="intel-darwin-10*"/>
             <toolset name="intel-linux-10*"/>
             <toolset name="gcc-4.3.4_0x"/>
             <toolset name="pathscale-3.2"/>
@@ -4937,7 +5009,7 @@ These tests will fail in most compilers that don't support rvalue references.
              Probably work-round-able if someone would care to look into these.
           </note>
        </mark-expected-failures>
-       <mark-expected-failures>
+        <mark-expected-failures>
             <test name="function_traits_test"/>
             <test name="remove_bounds_test"/>
             <test name="remove_const_test"/>
@@ -5175,7 +5247,7 @@ These tests will fail in most compilers that don't support rvalue references.
              be work-round-able if anyone cares enough to look into them.
           </note>
        </mark-expected-failures>
-       <mark-expected-failures>
+        <mark-expected-failures>
             <test name="test_mem_fn_tricky"/>
             <test name="test_bind_tricky"/>
             <test name="test_ref_wrapper_tricky"/>
@@ -5810,7 +5882,7 @@ These tests will fail in most compilers that don't support rvalue references.
             Related Boost mailing list discussion:
             http://lists.boost.org/Archives/boost/2008/11/144465.php
             CodeGear bug reports on this issue:
-            http://qc.codegear.com/wc/qcmain.aspx?d=68959  
+            http://qc.codegear.com/wc/qcmain.aspx?d=68959
             http://qc.codegear.com/wc/qcmain.aspx?d=69196
           </note>
         </mark-expected-failures>
@@ -5822,7 +5894,7 @@ These tests will fail in most compilers that don't support rvalue references.
             Borland 5.9.3 has an error (E2285) when trying to pass a
             multi-dimensional array by reference to a function template.
             A bug report by Christopher Yeleighton appears related:
-            "The compiler obligatorily converts member arrays to pointers" 
+            "The compiler obligatorily converts member arrays to pointers"
             http://qc.codegear.com/wc/qcmain.aspx?d=10267
           </note>
         </mark-expected-failures>
@@ -5864,6 +5936,17 @@ These tests will fail in most compilers that don't support rvalue references.
                 <note refid="3" author="D. Gregor"/>
             </mark-failure>
         </test>
+        <test name="value_init_test">
+          <mark-failure>
+            <toolset name="intel-9.0*"/>
+            <toolset name="intel-linux-9.0*"/>
+            <note author="Niels Dekker" date="2009-07-01">
+            When I made the conversion from value_initialized&lt;T&gt; to T&amp;
+            const-correct, this specific compiler version gave compile errors.
+            See also: Ticket #2548 - "Let's fix the logical constness of value_initialized!"
+            </note>
+          </mark-failure>
+        </test>
         <mark-expected-failures>
             <test name="value_init_test"/>
             <toolset name="msvc-6.5*"/>
@@ -5888,7 +5971,6 @@ These tests will fail in most compilers that don't support rvalue references.
         </mark-expected-failures>
     </library>
 
-
     <!-- uuid -->
     <library name="uuid">
         <mark-expected-failures>
@@ -5933,7 +6015,7 @@ These tests will fail in most compilers that don't support rvalue references.
             <test name="test_include1"/>
             <toolset name="borland-6.2.1"/>
             <note author="Andy Tompkins">
-                 The test relies on Boost.Iterator (iterator_facade) 
+                 The test relies on Boost.Iterator (iterator_facade)
                  which is not supported on this toolset.
            </note>
         </mark-expected-failures>
@@ -6349,4 +6431,9 @@ These tests will fail in most compilers that don't support rvalue references.
         This test fails when BOOST_UBLAS_NO_NESTED_CLASS_RELATION is defined.
     </note>
 
+    <note id="49">
+        This test fails because MinGW apparently does not always catch exceptions properly.
+    </note>
+
 </explicit-failures-markup>
+

粤ICP备19079148号