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 middle-end/41953] missing uninitialized warning (SRA,VOP) Date: Thu, 25 Mar 2021 13:41:31 +0000 [thread overview] Message-ID: <bug-41953-4-zyaCvw0E1q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41953-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41953 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2009-11-06 10:02:19 |2021-3-25 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Reconfirmed with -O2 -fno-tree-pre -fno-tree-sra or -O -fno-tree-sra. Basically the IL not warning is int f (const struct ExtentsBase & e1, int n) { struct ExtentsBase my_extents; int _1; int _7; <bb 2> [local count: 1073741824]: if (n_3(D) != 0) goto <bb 3>; [50.00%] else goto <bb 5>; [50.00%] <bb 5> [local count: 536870912]: goto <bb 4>; [100.00%] <bb 3> [local count: 536870913]: _1 = e1_5(D)->startx_; my_extents.startx_ = _1; <bb 4> [local count: 1073741824]: _7 = my_extents.startx_; my_extents ={v} {CLOBBER}; return _7; } while we for example warn for (PRE enabled): int f (const struct ExtentsBase & e1, int n) { struct ExtentsBase my_extents; int _1; int pretmp_9; int prephitmp_10; <bb 2> [local count: 1073741824]: if (n_3(D) != 0) goto <bb 4>; [50.00%] else goto <bb 3>; [50.00%] <bb 3> [local count: 536870912]: pretmp_9 = my_extents.startx_; goto <bb 5>; [100.00%] <bb 4> [local count: 536870913]: _1 = e1_5(D)->startx_; <bb 5> [local count: 1073741824]: # prephitmp_10 = PHI <pretmp_9(3), _1(4)> my_extents ={v} {CLOBBER}; return prephitmp_10;
parent reply other threads:[~2021-03-25 13:41 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-41953-4@http.gcc.gnu.org/bugzilla/>]
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-41953-4-zyaCvw0E1q@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).