|
5 | 5 | # The libc symbol that implements a particular standard interface is |
6 | 6 | # implementation-dependent. For example, strncpy() shows up as "__GI_strncpy" |
7 | 7 | # on some platforms. Use wildcards to avoid mentioning such specific names. |
| 8 | +# Avoid mentioning functions that are good candidates for inlining, |
| 9 | +# particularly single-caller static functions. Suppressions mentioning them |
| 10 | +# would be ineffective at higher optimization levels. |
8 | 11 |
|
9 | 12 |
|
10 | 13 | # We have occasion to write raw binary structures to disk or to the network. |
|
63 | 66 | fun:write_relcache_init_file |
64 | 67 | } |
65 | 68 |
|
| 69 | +{ |
| 70 | +padding_reorderbuffer_serialize |
| 71 | +Memcheck:Param |
| 72 | +write(buf) |
| 73 | + |
| 74 | +... |
| 75 | +fun:ReorderBufferSerializeTXN |
| 76 | +} |
| 77 | + |
66 | 78 |
|
67 | 79 | # gcc on ppc64 can generate a four-byte read to fetch the final "char" fields |
68 | 80 | # of a FormData_pg_cast. This is valid compiler behavior, because a proper |
|