public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arequipeno at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/58698] Spurious "may be used unitialized" warning when compiling with -Os Date: Sat, 12 Oct 2013 03:11:00 -0000 [thread overview] Message-ID: <bug-58698-4-JB61jsryiY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58698-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58698 --- Comment #3 from Ian Pilcher <arequipeno at gmail dot com> --- Created attachment 30989 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30989&action=edit Preprocessed file
next prev parent reply other threads:[~2013-10-12 3:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-12 3:09 [Bug c/58698] New: " arequipeno at gmail dot com 2013-10-12 3:10 ` [Bug c/58698] " arequipeno at gmail dot com 2013-10-12 3:11 ` arequipeno at gmail dot com [this message] 2013-10-12 3:13 ` arequipeno at gmail dot com 2013-10-12 19:50 ` [Bug tree-optimization/58698] " pinskia at gcc dot gnu.org 2013-10-14 9:05 ` [Bug tree-optimization/58698] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2013-10-14 16:50 ` law at redhat dot com 2013-11-05 15:00 ` rguenth at gcc dot gnu.org 2013-11-19 22:18 ` law at redhat dot com
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-58698-4-JB61jsryiY@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).