diff options
| author | Tomas Vondra | 2019-01-19 19:41:48 +0000 |
|---|---|---|
| committer | Tomas Vondra | 2019-01-19 19:41:48 +0000 |
| commit | 7990922413cab67b34780bd3454f0881b1fd8397 (patch) | |
| tree | 63bc04ad38b6b20ece9fe6f0a418ed9f9b1a4006 | |
| parent | dc2dee438015ad390528c5c6f2d0118d248196f0 (diff) | |
Revert "Add valgrind suppressions for wcsrtombs optimizations"
This reverts commit f57b94d9d0bbf42a18690d820f884dc0fc6bf79e.
Per discussion, it's not desirable to add valgrind suppressions for
outside our own code base (e.g. glibc in this case), especially when
the suppressions may be platform-specific. There are better ways to
deal with that, e.g. by providing local suppressions.
Discussion: https://www.postgresql.org/message-id/flat/90ac0452-e907-e7a4-b3c8-15bd33780e62%402ndquadrant.com
| -rw-r--r-- | src/tools/valgrind.supp | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/src/tools/valgrind.supp b/src/tools/valgrind.supp index 0c3cbbedafe..f0436789275 100644 --- a/src/tools/valgrind.supp +++ b/src/tools/valgrind.supp @@ -212,39 +212,3 @@ Memcheck:Cond fun:PyObject_Realloc } - -# wcsrtombs uses some clever optimizations internally, which to valgrind -# may look like access to uninitialized data. For example AVX2 instructions -# load data in 256-bit chunks, irrespectedly of wchar length. gconv does -# somethink similar by loading data in 32bit chunks and then shifting the -# data internally. Neither of those actually uses the uninitialized part -# of the buffer, as far as we know. -# -# https://www.postgresql.org/message-id/90ac0452-e907-e7a4-b3c8-15bd33780e62@2ndquadrant.com - -{ - wcsnlen_optimized - Memcheck:Cond - ... - fun:wcsrtombs - fun:wcstombs - fun:wchar2char -} - -{ - wcsnlen_optimized_addr32 - Memcheck:Addr32 - ... - fun:wcsrtombs - fun:wcstombs - fun:wchar2char -} - -{ - gconv_transform_internal - Memcheck:Cond - fun:__gconv_transform_internal_utf8 - fun:wcsrtombs - fun:wcstombs - fun:wchar2char -} |