public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gbburkhardt at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53480] New: warning "may be used uninitialized" issued with -m32 but not with -m64 Date: Thu, 24 May 2012 19:35:00 -0000 [thread overview] Message-ID: <bug-53480-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53480 Bug #: 53480 Summary: warning "may be used uninitialized" issued with -m32 but not with -m64 Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: gbburkhardt@verizon.net For the following program, a warning is issued with "-m32", but not with "-m64". armis@armis-00:~$ gcc -c -O2 -g -Wall -m32 -std=gnu99 tt.c tt.c: In function ‘sub’: tt.c:18:29: warning: ‘v0.minValue’ may be used uninitialized in this function [-Wuninitialized] tt.c:21:29: warning: ‘v0.maxValue’ may be used uninitialized in this function [-Wuninitialized] armis@armis-00:~$ gcc -c -O2 -g -Wall -m64 -std=gnu99 tt.c armis@armis-00:~$ #include <stdio.h> typedef struct { double minValue, maxValue; } Range; void getNewRange(Range*); void sub() { Range v0, v1; for (int i=0; i < 2; i++) { getNewRange(&v1); if (i == 0) { v0.minValue = v1.minValue; v0.maxValue = v1.minValue; } else { if (v0.minValue > v1.minValue) v0.minValue = v1.minValue; if (v0.maxValue < v1.maxValue) v0.maxValue = v1.maxValue; } } printf("min=%f, max=%f\n", v0.minValue, v0.maxValue); } armis@armis-00:~$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6.1/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.1-9ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
next reply other threads:[~2012-05-24 19:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-24 19:35 gbburkhardt at verizon dot net [this message] 2012-05-24 19:46 ` [Bug tree-optimization/53480] " pinskia at gcc dot gnu.org 2012-05-26 18:09 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53480-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).