Re: [Boost-bugs] [Boost C++ Libraries] #10446: boost 1.56 compile fail with atomics failure

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #10446: boost 1.56 compile fail with atomics failure
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-09-23 06:47:30

#10446: boost 1.56 compile fail with atomics failure
--------------------------------+--------------------------
  Reporter:  niqingliang2003@…  |      Owner:  timblechmann
      Type:  Bugs               |     Status:  new
 Milestone:  To Be Determined   |  Component:  atomic
   Version:  Boost 1.56.0       |   Severity:  Problem
Resolution:                     |   Keywords:  atomic
--------------------------------+--------------------------
Changes (by andysem):

 * cc: Andrey.Semashev@… (added)

Comment:

 @niqingliang2003:

 I suspect that for some reason the compiler doesn't support atomic bools,
 but does support some other size atomics. Could you attach the output of
 the following command:

 {{{
 gcc -march=armv6  -dM -E - < /dev/null
 }}}

 Note the -march=armv6 argument - please specify it exactly as you do when
 compiling Boost (or don't specify it if you don't when building Boost).

 > I think 'BOOST_ATOMIC_THREAD_FENCE' should depend on
 'BOOST_ATOMIC_FLAG_LOCK_FREE', do you think so?

 No, it shouldn't. These macros are responsible for different features that
 are strictly speaking unrelated. More practically, I guess, every platform
 that supports atomic instructions can implement fences.

 @mrwombat: You might need to explicitly add an -march=... argument. I'm
 not sure what target architecture is used by default.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/10446#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.