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/107411] trivial-auto-var-init=zero invalid uninitialized variable warning
Date: Fri, 28 Oct 2022 11:31:48 +0000 [thread overview]
Message-ID: <bug-107411-4-upO1ouQJ1E@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |24639
CC| |qing.zhao at oracle dot com,
| |rguenth at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> 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.
We diagnose the
D.2374 = _1;
store which uses uninitialized _1. The FE emits
<<cleanup_point <<< Unknown tree: expr_stmt
(void) (e = D.2389 = t ();, (const int &) &D.2389;) >>>>>;
<<cleanup_point <<< Unknown tree: expr_stmt
f ((int) *e) >>>>>;
note that without -ftrivial-auto-var-init=zero we see
<bb 2> :
_6 = t ();
<bb 3> :
_1 = _6;
D.2389 = _1;
e_8 = &D.2389;
_2 = *e_8;
f (_2);
<bb 4> :
D.2389 ={v} {CLOBBER(eol)};
return;
<bb 5> :
<L0>:
D.2389 ={v} {CLOBBER(eol)};
resx 1
while with the flag we have
<bb 2> :
_1 = .DEFERRED_INIT (4, 2, &"D.2389"[0]);
D.2389 = _1;
e_7 = .DEFERRED_INIT (8, 2, &"e"[0]);
_9 = t ();
<bb 3> :
_2 = _9;
D.2389 = _2;
e_11 = &D.2389;
_3 = *e_11;
f (_3);
<bb 4> :
D.2389 ={v} {CLOBBER(eol)};
return;
<bb 5> :
<L0>:
D.2389 ={v} {CLOBBER(eol)};
resx 1
The gimplifier instead of
_1 = t ();
D.2389 = _1;
e = &D.2389;
_2 = *e;
f (_2);
produces
_1 = .DEFERRED_INIT (4, 2, &"D.2389"[0]);
D.2389 = _1;
e = .DEFERRED_INIT (8, 2, &"e"[0]);
_2 = t ();
D.2389 = _2;
e = &D.2389;
_3 = *e;
f (_3);
which is odd and sub-optimal at least. Doing such things makes us rely
on DSE to elide the uninit "inits".
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
[Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next prev parent reply other threads:[~2022-10-28 11:31 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 ` [Bug middle-end/107411] " pinskia at gcc dot gnu.org
2022-10-28 11:31 ` rguenth at gcc dot gnu.org [this message]
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-upO1ouQJ1E@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: link
Be 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).