diff options
author | Borislav Petkov <bbpetkov@yahoo.de> | 2007-05-06 14:49:17 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-05-07 12:12:52 -0700 |
commit | 9490991482a2091a828d997adbc088e24c310a4d (patch) | |
tree | dcdd9febee63e82cd792250a8a4c4dd8e6aab4be /include/linux/compiler-gcc3.h | |
parent | a8127717cb24be7b8827a8d9e0ddbfde6b392146 (diff) | |
download | kernel_samsung_espresso10-9490991482a2091a828d997adbc088e24c310a4d.zip kernel_samsung_espresso10-9490991482a2091a828d997adbc088e24c310a4d.tar.gz kernel_samsung_espresso10-9490991482a2091a828d997adbc088e24c310a4d.tar.bz2 |
Add unitialized_var() macro for suppressing gcc warnings
Introduce a macro for suppressing gcc from generating a warning about a
probable uninitialized state of a variable.
Example:
- spinlock_t *ptl;
+ spinlock_t *uninitialized_var(ptl);
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@yahoo.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/compiler-gcc3.h')
-rw-r--r-- | include/linux/compiler-gcc3.h | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/include/linux/compiler-gcc3.h b/include/linux/compiler-gcc3.h index 1698b84..ecd621f 100644 --- a/include/linux/compiler-gcc3.h +++ b/include/linux/compiler-gcc3.h @@ -13,4 +13,10 @@ #define __must_check __attribute__((warn_unused_result)) #endif +/* + * A trick to suppress uninitialized variable warning without generating any + * code + */ +#define uninitialized_var(x) x = x + #define __always_inline inline __attribute__((always_inline)) |