public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/43361] missing uninitialized warning without optimization (-O0) (PHI in always_executed basic block) Date: Mon, 29 Mar 2021 17:19:44 +0000 [thread overview] Message-ID: <bug-43361-4-rhqz513JwF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-43361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43361 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2010-03-14 15:45:50 |2021-3-29 --- Comment #14 from Martin Sebor <msebor at gcc dot gnu.org> --- Reconfirmed with GCC 11 and the C test case below: void f (int); int main () { int i; int array[10]; for (; i<10; ++i) { // no warning f (i); // no warning array [i] = i; // no warning, really hurts } }
next prev parent reply other threads:[~2021-03-29 17:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43361-4@http.gcc.gnu.org/bugzilla/> 2011-09-28 22:54 ` [Bug c++/43361] missing uninitialized warning without optimization (loop representation) paolo.carlini at oracle dot com 2013-10-21 12:08 ` manu at gcc dot gnu.org 2021-03-29 17:19 ` msebor at gcc dot gnu.org [this message] 2021-03-30 7:10 ` [Bug tree-optimization/43361] missing uninitialized warning without optimization (-O0) (PHI in always_executed basic block) rguenth at gcc dot gnu.org 2022-08-29 13:25 ` rguenth 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-43361-4-rhqz513JwF@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).