Re: [boost] [atomic] gcc-atomic.hpp errors with Clang 3.4

Subject: Re: [boost] [atomic] gcc-atomic.hpp errors with Clang 3.4
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-03-12 15:33:19

On Wed, Mar 12, 2014 at 10:34 PM, Richard Hadsell
<hadsell_at_[hidden]> wrote:
> I am trying to build Boost 1.55 libraries with Clang 3.4 using g++ 4.8.2 as
> the toolchain on CentOS 6.5.  I think these errors arise from trying to
> initialize 128-bit integers with 0:

[snip]

> Similar errors follow these.

This has been already fixed in git. The fix will be released in 1.56.

> I think the initializations to 0 are superfluous, because they are followed
> by memcpy calls that overwrite them.

The actual value may be smaller than the storage type, so the storage
is initialized to avoid compilers and tools like valgrind complaining
about using uninitialized memory.