On 2006-10-24, Douglas Gregor <dgregor@cs.indiana.edu> wrote:
Boost Regression test failures Report time: 2006-10-24T10:41:49Z [...] |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64
These are not going to go away unless either: 1. they are marked as expected 2. the test is reworked to avoid the problem 3. the macro BOOST_MPL_ASSERT_RELATION is reworked to avoid the problem See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29518 The macro is: #define BOOST_MPL_ASSERT(pred) \ enum { \ BOOST_PP_CAT(mpl_assertion_in_line_,__LINE__) = sizeof( \ boost::mpl::assertion_failed<false>( \ boost::mpl::assert_arg( (void (*) pred)0, 1 ) \ ) \ ) \ }\ /**/ It is apparently to do with the enum usage... I'm guessing there is a good reason why this code (and others in the boost/mpl/assert.hpp) uses enum directly rather than BOOST_STATIC_CONSTANT? phil -- change name before "@" to "phil" for email