The patch titled
Add unitialized_var() macro for suppressing gcc warnings
has been added to the -mm tree. Its filename is
add-unitialized_var-macro-for-suppressing-gcc-warnings.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Add unitialized_var() macro for suppressing gcc warnings
From: Borislav Petkov <bbpetkov@xxxxxxxx>
Introduce a macro for suppressing gcc from generating a warning about a
probable uninitialized state of a variable.
Not a happy solution, but those warnings are obnoxious.
- Using the usual pointlessly-set-it-to-zero approach wastes several
bytes of text.
- Using a macro means we can (hopefully) do something else if gcc changes
cause the `x = x' hack to stop working
- Using a macro means that people who are worried about hiding true bugs
can easily turn it off.
Signed-off-by: Borislav Petkov <bbpetkov@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/compiler.h | 2 ++
1 file changed, 2 insertions(+)
diff -puN include/linux/compiler.h~add-unitialized_var-macro-for-suppressing-gcc-warnings include/linux/compiler.h
--- a/include/linux/compiler.h~add-unitialized_var-macro-for-suppressing-gcc-warnings
+++ a/include/linux/compiler.h
@@ -74,6 +74,8 @@ extern void __chk_io_ptr(const void __io
(typeof(ptr)) (__ptr + (off)); })
#endif
+#define uninitialized_var(x) x = x
+
#endif /* __KERNEL__ */
#endif /* __ASSEMBLY__ */
_
Patches currently in -mm which might be from bbpetkov@xxxxxxxx are
origin.patch
git-acpi.patch
add-unitialized_var-macro-for-suppressing-gcc-warnings.patch
kernel-doc-handle-arrays-with-arithmetic-expressions-as.patch
generate-main-index-page-when-building-htmldocs.patch
alphabetically-sorted-entries-in.patch
kill-warnings-when-building-mandocs.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
