Issue 110 in sparsehash: sparsehash is slower on a release build with asserts

[spars...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 110 by aadityak...@gmail.com: sparsehash is slower on a release
build with asserts
https://code.google.com/p/sparsehash/issues/detail?id=110

What steps will reproduce the problem?
1. Building with ASSERTS on in a Release environment.

What is the expected output? What do you see instead?
I expected dense_hash_set to beat the unordered_set even on an asserted
release build.

What version of the product are you using? On what operating system?
Sparsehash 2.0.2

Please provide any additional information below.
64-bit Linux, GCC 4.7.2, -O2 -std=c++11


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[spars...@googlecode.com]

Comment #1 on issue 110 by aadityak...@gmail.com: sparsehash is slower on a

release build with asserts
https://code.google.com/p/sparsehash/issues/detail?id=110

In my build environment, we run our test suite for regression and
performance regression tests with an ASSERTed build with optimizations on.

I am unsure as to what I expect the end result of this issue to be. My hope
was that the liberal use of the asserts would be turned on only when NDEBUG
is not defined.

[1971 powerChina]

give you advice for this net :http://sourceforge.net/projects/pwwhashmap/