[lkml]   [2011]   [Jul]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] TRACING: Fix a copmile warning

[adding gcc-help@ to the Cc: list]

On Mon, Jul 25, 2011 at 6:38 PM, Arnaud Lacombe <> wrote:
> Hi,
> On Mon, Jul 25, 2011 at 4:19 PM, Steven Rostedt <> wrote:
>> On Mon, 2011-07-25 at 15:43 -0400, Arnaud Lacombe wrote:
>>> Actually, we have a special uninitialized_var(x) macro to handle such
>>> false positive. From include/linux/compiler-gcc.h:
>>> /*
>>>  * A trick to suppress uninitialized variable warning without generating any
>>>  * code
>>>  */
>>> #define uninitialized_var(x) x = x
>> I'm aware of that too, but I think that is inappropriate as well. As I
>> said, some versions of gcc report it, others don't. Seems that gcc 4.6.0
>> says this is an error where 4.5.1 does not (I just tried both).
gcc will only emits the warning at -Os. It seems to me that the
resulting code clearly ends-up testing an uninitialized value, ie.
assuming the following test-case:

extern void *e(void);
extern void *f(void);
extern void g(void);

void fn(void)
void *b, *a;

a = e();
if (a != 0)
b = f();
if (a != 0 && b != 0)

gcc 4.5.1 will generates the following x86-32 assembly:

% gcc -m32 -Wall -Os -c -S -o - kernel/trace/trace_printk.c
.file "trace_printk.c"
kernel/trace/trace_printk.c: In function 'fn':
kernel/trace/trace_printk.c:7:8: warning: 'b' may be used
uninitialized in this function
.globl fn
.type fn, @function
pushl %ebp
movl %esp, %ebp
pushl %esi
pushl %ebx
call e
testl %eax, %eax
movl %eax, %ebx
je .L2
call f
movl %eax, %esi
testl %esi, %esi
je .L1
testl %ebx, %ebx
je .L1
popl %ebx
popl %esi
popl %ebp
jmp g
popl %ebx
popl %esi
popl %ebp
.size fn, .-fn
.ident "GCC: (GNU) 4.5.1 20100924 (Red Hat 4.5.1-4)"
.section .note.GNU-stack,"",@progbits

It seems gcc transforms the conditional from:

if (a != NULL && b != NULL) ...


if (b != NULL && a != NULL) ...

In which case the warning is fully valid. I'm not sure what's the C
standard guarantee in term of conditional test order. gcc 4.7.0 has
the same behavior.

- Arnaud
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-07-26 01:53    [W:0.080 / U:9.836 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site