sparsehash is slower on a release build with asserts
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
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
Original issue reported on code.google.com by aadityak...@gmail.com
on 9 Jun 2015 at 3:44
Google Code Exporter commented
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.
Original comment by aadityak...@gmail.com
on 9 Jun 2015 at 3:46