Home | History | Annotate | Download | only in info

Lines Matching full:uninitialized

551           -Winit-self  -Winline -Wmaybe-uninitialized
555 -Wmain -Wmaybe-uninitialized -Wmissing-braces -Wmissing-field-initializers
2114 Put uninitialized or runtime-initialized global variables into the
3040 -Wmaybe-uninitialized
3232 Warn about uninitialized variables which are initialized with
3236 For example, GCC will warn about `i' being uninitialized in the
3596 If you want to warn about code which uses the uninitialized value
3600 These warnings occur for individual uninitialized or clobbered
3602 variables which are uninitialized or clobbered as a whole. They do
3613 `-Wmaybe-uninitialized'
3617 emit a warning if it can not prove the uninitialized paths do not
14439 Put uninitialized `const' variables in the read-only data section.
15678 to by register `r13'. Put small uninitialized global and static
15687 register `r13'. Put small uninitialized global and static data in
15700 in the `.sdata' section. Put small uninitialized global data in
15708 data in the `.data' section, and all uninitialized data in the
17244 In C code, controls the placement of uninitialized global
17252 compiler should place uninitialized global variables in the data
17260 on other systems which always treat uninitialized variable
21166 uninitialized variables.
22469 uninitialized global variables but the linker requires each object
22470 be defined once, with the exception that uninitialized variables
22474 issue an error if an uninitialized variable has multiple
46886 * Wmaybe-uninitialized: Warning Options. (line 711)
46953 * Wno-maybe-uninitialized: Warning Options. (line 711)
47040 * Wno-uninitialized: Warning Options. (line 688)