summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorJan Janssen <medhefgo@web.de>2023-01-07 22:16:52 +0100
committerLennart Poettering <lennart@poettering.net>2023-01-09 18:58:54 +0100
commit3f92dc2fd4070b213e6bc85263a9bef06ec9a486 (patch)
tree63f4106441053a06868aab1c5a5e6d13c42a4b4f /.github
parentf977356a82822612d82a8b4507b5140a7a6ffc40 (diff)
downloadsystemd-3f92dc2fd4070b213e6bc85263a9bef06ec9a486.tar.gz
boot: Simplify object erasure
This erase_obj() machinery looks like voodoo and creates an awful lot of noise as soon as we get back to building with -O0. We can do this in a more simple way by introducing a struct that holds the information we need on cleanup. When building with optimization enabled, all this gets inlined and the eraser vanishes.
Diffstat (limited to '.github')
-rw-r--r--.github/codeql-queries/UninitializedVariableWithCleanup.ql2
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/codeql-queries/UninitializedVariableWithCleanup.ql b/.github/codeql-queries/UninitializedVariableWithCleanup.ql
index dadc6cb1b5..e514111f28 100644
--- a/.github/codeql-queries/UninitializedVariableWithCleanup.ql
+++ b/.github/codeql-queries/UninitializedVariableWithCleanup.ql
@@ -20,7 +20,7 @@ import semmle.code.cpp.controlflow.StackVariableReachability
* since they don't do anything illegal even when the variable is uninitialized
*/
predicate cleanupFunctionDenyList(string fun) {
- fun = "erase_char" or fun = "erase_obj"
+ fun = "erase_char"
}
/**