-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dont use AVX512 with asan #398
Conversation
555114f
to
666d92f
Compare
the problem doesnt reproduce with this branch |
@Yuval-Ariel Please add a comment explaining why you avoid using AVX512 when MUST_FREE_HEAP_ALLOCATIONS (== ASAN). |
666d92f
to
e9f809e
Compare
right you are, done |
Do we understand why this happens on the Speedb code and is not seen in Rocks? Is it a different test suite or something different? |
Unless I am mistaken, it does happen in RocksDB as well. This is a workaround that would let us test with ASAN. We should open an issue for RocksDB. |
yes, @udi-speedb is correct. |
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
the previous commit disabled all the rest of the XXH optimizations since it didnt prevent the XXH_VECTOR from being defined as XXH_AVX512.
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
the previous commit disabled all the rest of the XXH optimizations since it didnt prevent the XXH_VECTOR from being defined as XXH_AVX512.
fix - AXV512: don't use XXH3_accumulate_512 with ASAN (#398) the previous commit disabled all the rest of the XXH optimizations since it didnt prevent the XXH_VECTOR from being defined as XXH_AVX512.
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
fix - AXV512: don't use XXH3_accumulate_512 with ASAN (#398) the previous commit disabled all the rest of the XXH optimizations since it didnt prevent the XXH_VECTOR from being defined as XXH_AVX512.
avoid these functions when running with ASAN since they caused errors in the stress test. this happens in rocksdb as well and this is only meant as a workaround to continue ASAN testing.
fix - AXV512: don't use XXH3_accumulate_512 with ASAN (#398) the previous commit disabled all the rest of the XXH optimizations since it didnt prevent the XXH_VECTOR from being defined as XXH_AVX512.
No description provided.