Valgrind failures in test4 with wchar_t support enabled about dynamic_bitset

[jwakely]

It's more likely that your valgrind doesn't know about the optimized AVX implementation of wmemchr in your libc, and they are false positives.

[jeking3]

Related:

https://www.e-learn.cn/content/wangluowenzhang/415811

[jeking3]

Given that the builds also fail on Windows with iostream related issues I am going to suggest the issue is in dynamic_bitset or the unit test until proven otherwise. If we can pass all our CI tests clean and we still see this in the docker environment with libstdc++ 7.3 (gcc-7.3) then we'll report it to valgrind.

Curiously they don't seem to fail with valgrind 3.10 and an older compiler combination on travis builds.

[jeking3]

Issue is resolved with a newer valgrind.