aboutgitcodebugslistschat
path: root/tap.c
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2024-09-05 21:22:04 +1000
committerStefano Brivio <sbrivio@redhat.com>2024-09-06 12:54:20 +0200
commit748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc (patch)
treee4340907a3108450a20c8133ec202f85a196624f /tap.c
parentafedc2412e8576d95ef49e684601bde2f12d7974 (diff)
downloadpasst-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar.gz
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar.bz2
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar.lz
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar.xz
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.tar.zst
passt-748ef4cd6e7d7307b4c91cbe59ad040ef535dbdc.zip
cppcheck: Work around some cppcheck 2.15.0 redundantInitialization warnings
cppcheck-2.15.0 has apparently broadened when it throws a warning about redundant initialization to include some cases where we have an initializer for some fields, but then set other fields in the function body. This is arguably a false positive: although we are technically overwriting the zero-initialization the compiler supplies for fields not explicitly initialized, this sort of construct makes sense when there are some fields we know at the top of the function where the initializer is, but others that require more complex calculation. That said, in the two places this shows up, it's pretty easy to work around. The results are arguably slightly clearer than what we had, since they move the parts of the initialization closer together. So do that rather than having ugly suppressions or dealing with the tedious process of reporting a cppcheck false positive. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'tap.c')
0 files changed, 0 insertions, 0 deletions