public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107411] trivial-auto-var-init=zero invalid uninitialized variable warning Date: Wed, 26 Oct 2022 17:52:50 +0000 [thread overview] Message-ID: <bug-107411-4-Sruao9itme@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107411-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107411 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-10-26 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. reduced testcase: int t(); void f(int); void j() { const int& e = t(); f(e); } Someone who understands the uininit pass should look into this but the IR at that point we get is (with -fno-exceptions due to extra clobbers otherwise which don't make a difference): _1 = .DEFERRED_INIT (4, 2, &"D.2374"[0]); D.2374 = _1; e_6 = .DEFERRED_INIT (8, 2, &"e"[0]); _2 = t (); D.2374 = _2; e_9 = &D.2374; _3 = *e_9; f (_3); D.2374 ={v} {CLOBBER(eol)}; There is no read from D.2374 in the call to t at all and then we do a full write after the call.
next prev parent reply other threads:[~2022-10-26 17:52 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 9:10 [Bug c++/107411] New: " davidwelch158 at hotmail dot com 2022-10-26 17:52 ` pinskia at gcc dot gnu.org [this message] 2022-10-28 11:31 ` [Bug middle-end/107411] " rguenth at gcc dot gnu.org 2022-10-28 14:15 ` qinzhao at gcc dot gnu.org 2022-11-21 15:35 ` pinskia at gcc dot gnu.org 2023-02-14 0:03 ` pinskia at gcc dot gnu.org 2023-02-15 19:21 ` qinzhao at gcc dot gnu.org 2023-02-16 7:35 ` rguenther at suse dot de 2023-02-16 14:30 ` qing.zhao at oracle dot com 2023-02-16 20:18 ` qinzhao at gcc dot gnu.org 2023-02-16 20:18 ` qinzhao at gcc dot gnu.org 2023-02-16 20:55 ` jakub at gcc dot gnu.org 2023-02-16 21:53 ` qinzhao at gcc dot gnu.org 2023-02-17 7:32 ` rguenther at suse dot de 2023-02-28 17:11 ` cvs-commit at gcc dot gnu.org 2023-02-28 17:13 ` qinzhao 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-107411-4-Sruao9itme@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).