Bug 6050 - Possible use of uninitialized value in __syscall_error.c
Summary: Possible use of uninitialized value in __syscall_error.c
Status: NEW
Alias: None
Product: uClibc
Classification: Unclassified
Component: Other (show other bugs)
Version: 0.9.33.3
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-03 03:47 UTC by Jeffrey Walton
Modified: 2013-03-03 03:47 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Walton 2013-03-03 03:47:18 UTC 
CC=clang

  CC libc/sysdeps/linux/x86_64/__syscall_error.os
libc/sysdeps/linux/x86_64/__syscall_error.c:19:14: warning: variable 'err_no' is
      uninitialized when used here [-Wuninitialized]
        __set_errno(err_no);
        ~~~~~~~~~~~~^~~~~~~
./include/errno.h:79:36: note: expanded from macro '__set_errno'
#define __set_errno(val) (errno = (val))
                                   ^
libc/sysdeps/linux/x86_64/__syscall_error.c:16:21: note: initialize the variable
      'err_no' to silence this warning
        register int err_no __asm__ ("%rcx");
                           ^
                            = 0       
1 warning generated.