CEPH filesystem development
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Clangs is complaining about type evaluations in test_mempool.cc
Date: Wed, 28 Dec 2016 00:29:17 +0100	[thread overview]
Message-ID: <d8b38e75-71fc-42e0-6095-5c89994ed2ea@digiware.nl> (raw)
In-Reply-To: <20161227161914.GA19064@ultraspiritum.eng.arb.redhat.com>

On 27-12-2016 17:19, Adam C. Emerson wrote:
> On 27/12/2016, Willem Jan Withagen wrote:
>> Perhaps somebody has a suggestion on how to fix this??
> 
> I suspect that the container changes in
> https://github.com/ceph/ceph/pull/12626 will fix it. The denc container
> encodings in master always assume the default compare and allocator
> parameters.
> 

Eh, nope,....

Clang still complains about the same thing.
It is still complaining about a type comparison, and type not being
compatible.

--WjW

/usr/bin/CC   -DCEPH_LIBDIR=\"/usr/local/lib\"
-DCEPH_PKGLIBDIR=\"/usr/local/lib/ceph\"
-I/usr/srcs/Ceph/work/ceph/build/src/include
-I/usr/srcs/Ceph/work/ceph/src -isystem /usr/local/include -isystem
/usr/srcs/Ceph/work/ceph/build/include
-I/usr/srcs/Ceph/work/ceph/src/xxHash
-I/usr/srcs/Ceph/work/ceph/src/googletest/googlemock/include
-I/usr/srcs/Ceph/work/ceph/src/googletest/googletest/include  -Wall
-Wtype-limits -Wignored-qualifiers -Winit-self -Wpointer-arith
-Werror=format-security -fno-strict-aliasing -fsigned-char
-Wno-unused-function -Wno-unused-local-typedef -Wno-varargs
-Wno-gnu-designator -Wno-missing-braces -Wno-parentheses
-Wno-deprecated-register  -ftemplate-depth-1024 -Wno-invalid-offsetof
-Wnon-virtual-dtor -Wno-inconsistent-missing-override
-Wno-mismatched-tags -Wno-unused-private-field -fdiagnostics-color=auto
-I/usr/local/include/nss/nss -I/usr/local/include/nspr
-fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc
-fno-builtin-free -Wno-null-dereference -O0 -g -fPIE   -DHAVE_CONFIG_H
-D__CEPH__ -D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS
-I/usr/srcs/Ceph/work/ceph/src/googletest/googlemock/include
-I/usr/srcs/Ceph/work/ceph/build/src/googletest/googlemock/include
-I/usr/srcs/Ceph/work/ceph/src/googletest/googletest/include
-I/usr/srcs/Ceph/work/ceph/build/src/googletest/googletest/include
-fno-strict-aliasing -std=c++11 -o
CMakeFiles/unittest_mempool.dir/test_mempool.cc.o -c
/usr/srcs/Ceph/work/ceph/src/test/test_mempool.cc
In file included from /usr/srcs/Ceph/work/ceph/src/test/test_mempool.cc:20:
In file included from
/usr/srcs/Ceph/work/ceph/src/common/ceph_argparse.h:31:
In file included from /usr/srcs/Ceph/work/ceph/src/common/entity_name.h:22:
In file included from /usr/srcs/Ceph/work/ceph/src/include/encoding.h:25:
In file included from /usr/srcs/Ceph/work/ceph/src/include/denc.h:29:
/usr/include/c++/v1/map:837:5: error: static_assert failed
"Allocator::value_type must be same type as value_type"
    static_assert((is_same<typename allocator_type::value_type,
value_type>::value),
    ^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/srcs/Ceph/work/ceph/src/test/test_mempool.cc:235:39: note: in
instantiation of template class 'std::__1::map<int, int,
std::__1::less<int>,
mempool::pool_allocator<mempool::pool_index_t::mempool_unittest_1,
std::__1::pair<int, int> > >' requested here
    mempool::unittest_1::map<int,int> v;
                                      ^


      reply	other threads:[~2016-12-27 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27  9:35 Clangs is complaining about type evaluations in test_mempool.cc Willem Jan Withagen
2016-12-27 16:19 ` Adam C. Emerson
2016-12-27 23:29   ` Willem Jan Withagen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d8b38e75-71fc-42e0-6095-5c89994ed2ea@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox