public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32132] New: bogus warning at -O3 ( 'r' may be used uninitialized in this function ). Date: Mon, 28 May 2007 20:08:00 -0000 [thread overview] Message-ID: <bug-32132-7667@http.gcc.gnu.org/bugzilla/> (raw) attached testcase produces unexpected warning at -O3: $ g++ -Wall -Woverloaded-virtual -Werror -O3 -gdwarf-2 -g1 -fPIE \ -Wno-error -c auHexCastTest.ii ../../au/h/auHexCast.hpp: In function ‘R au::hex_cast(const stlp_std::string&) [with R = int]’: ../../au/h/auHexCast.hpp:50: warning: ‘r’ may be used uninitialized in this function -- Summary: bogus warning at -O3 ( 'r' may be used uninitialized in this function ). Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pluto at agmk dot net GCC target triplet: x86_64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32132
next reply other threads:[~2007-05-28 20:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-28 20:08 pluto at agmk dot net [this message] 2007-05-28 20:09 ` [Bug c++/32132] " pluto at agmk dot net 2007-05-28 20:13 ` pinskia at gcc dot gnu dot org 2007-05-28 20:16 ` pluto at agmk dot net 2007-05-28 20:26 ` pinskia at gcc dot gnu dot org 2007-05-28 21:48 ` pinskia at gcc dot gnu dot org 2007-05-29 8:51 ` pluto at agmk dot net 2007-05-29 10:18 ` pluto at agmk dot net 2007-05-29 12:31 ` manu at gcc dot gnu dot org 2007-05-29 12:35 ` pluto at agmk dot net 2007-05-29 12:42 ` pluto at agmk dot net 2007-05-29 12:57 ` manu at gcc dot gnu dot org 2007-06-10 3:19 ` pinskia at gcc dot gnu dot 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-32132-7667@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).