diff options
| author | Florian Weimer <fweimer@redhat.com> | 2024-04-13 16:17:38 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2024-04-13 17:42:13 +0200 |
| commit | aea52e3d2b71e89f2ba4fd4d8f1f8d3036d83c1d (patch) | |
| tree | a4d1718dd22e6fc0b757e4455fa4fe82bd2ccd66 /malloc/alloc_buffer_copy_bytes.c | |
| parent | cf11e74b0d81d389bcad5cdbba020ba475f0ac4b (diff) | |
| download | glibc-aea52e3d2b71e89f2ba4fd4d8f1f8d3036d83c1d.tar.xz glibc-aea52e3d2b71e89f2ba4fd4d8f1f8d3036d83c1d.zip | |
Revert "x86_64: Suppress false positive valgrind error"
This reverts commit a1735e0aa858f0c8b15e5ee9975bff4279423680.
The test failure is a real valgrind bug that needs to be fixed before
valgrind is usable with a glibc that has been built with
CC="gcc -march=x86-64-v3". The proposed valgrind patch teaches
valgrind to replace ld.so strcmp with an unoptimized scalar
implementation, thus avoiding any AVX2-related problems.
Valgrind bug: <https://bugs.kde.org/show_bug.cgi?id=485487>
Reviewed-by: H.J. Lu <hjl.tools@gmail.com>
Diffstat (limited to 'malloc/alloc_buffer_copy_bytes.c')
0 files changed, 0 insertions, 0 deletions