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/112766] [14 regression] spurious -Wmaybe-uninitialized with array new since r14-4089 Date: Thu, 30 Nov 2023 09:01:53 +0000 [thread overview] Message-ID: <bug-112766-4-BgUA8QRXU4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112766-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112766 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Keywords| |missed-optimization Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so one uninit use occurs on the exceptional path from Result::Result() during the initialization loop of the allocated array, this then has <bb 25> [count: 0]: # _71 = PHI <_58(21), _42(D)(6), _42(D)(45), _42(D)(14), _42(D)(24)> # _72 = PHI <_85(21), _43(D)(6), _43(D)(45), _43(D)(14), _43(D)(24)> # _73 = PHI <_44(D)(21), _44(D)(6), _41(45), _44(D)(14), _44(D)(24)> # nElements.2_74 = PHI <_17(21), _17(6), nElements.2_47(D)(45), nElements.2_47(D)(14), _17(24)> # cleanup.4_75 = PHI <1(21), 0(6), 0(45), 0(14), 0(24)> # nElements.6_76 = PHI <nElements.6_56(D)(21), nElements.6_56(D)(6), _17(45), _17(14), nElements.6_56(D)(24)> # cleanup.7_77 = PHI <0(21), 0(6), 1(45), 0(14), 0(24)> <L47>: resx 3 // goes to L25 <L25>: if (cleanup.7_77 != 0) goto <bb 27>; [0.00%] else goto <bb 46>; [0.00%] but somehow we are not seeing that cleanup.7_77 is 0 on all the paths n_Elements.6_76 are uninitialized. (We're also not threading this for unknown reasons, likely the threader not going up EH edges)
next prev parent reply other threads:[~2023-11-30 9:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-29 16:54 [Bug c++/112766] New: [14 regression] spurious -Wmaybe-uninitialized with array new sss@li-snyder.org 2023-11-29 17:04 ` [Bug tree-optimization/112766] " mpolacek at gcc dot gnu.org 2023-11-30 9:01 ` rguenth at gcc dot gnu.org [this message] 2023-11-30 9:50 ` [Bug tree-optimization/112766] [14 regression] spurious -Wmaybe-uninitialized with array new since r14-4089 rguenth at gcc dot gnu.org 2023-11-30 12:35 ` cvs-commit at gcc dot gnu.org 2023-11-30 12:35 ` 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-112766-4-BgUA8QRXU4@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).