public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59908] Incorrect uninit warning with -fsanitize=address caused by LIM Date: Wed, 29 Jan 2014 13:37:00 -0000 [thread overview] Message-ID: <bug-59908-4-ErtAZgGEOS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59908-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59908 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- There is a very old duplicate somewhere. Happens with store-motion for a simple void foo (int n) { int x, i; for (i = 0; i < n; ++i) x = i; bar (&x); } IIRC. Of course requires us to re-write x into SSA form later, so some more "clever" testcase is required. LIM does: <bb 2>: if (n_4(D) > 0) goto <bb 3>; else goto <bb 9>; <bb 3>: x_lsm.3_5 = x; ^^^^ load of uninitialized x <bb 4>: # i_11 = PHI <i_6(5), 0(3)> x_lsm.3_1 = i_11; i_6 = i_11 + 1; if (n_4(D) > i_6) goto <bb 5>; else goto <bb 10>; <bb 10>: # x_lsm.3_9 = PHI <x_lsm.3_1(4)> x = x_lsm.3_9; goto <bb 7>; now go find the duplicate ;)
next prev parent reply other threads:[~2014-01-29 13:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-22 17:14 [Bug tree-optimization/59908] New: " jakub at gcc dot gnu.org 2014-01-22 17:19 ` [Bug tree-optimization/59908] " mpolacek at gcc dot gnu.org 2014-01-29 13:37 ` rguenth at gcc dot gnu.org [this message] 2014-03-26 10:09 ` jakub at gcc dot gnu.org 2014-03-26 13:17 ` rguenth at gcc dot gnu.org 2014-04-22 11:37 ` jakub at gcc dot gnu.org 2014-07-16 13:30 ` jakub at gcc dot gnu.org 2014-10-30 10:41 ` jakub at gcc dot gnu.org 2015-06-26 19:57 ` jakub at gcc dot gnu.org 2015-06-26 20:35 ` jakub at gcc dot gnu.org 2021-08-08 4:45 ` 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-59908-4-ErtAZgGEOS@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).