public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103899] [12 Regression] make profiledbootstrap fails due to uninitialized warning in expr.c
Date: Wed, 05 Jan 2022 08:25:56 +0000 [thread overview]
Message-ID: <bug-103899-4-kzgdb31HVL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103899-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103899
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2022-01-05
CC| |aldyh at gcc dot gnu.org
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Reduced testcase:
> int h;
> int l ();
> int *k ();
> void nn ();
> void expand_expr_real_1 (int *exp)
> {
> int m;
> int *context;
> m = 2;
> if (h || !exp)
> m = l ();
> if (exp)
> context = k ();
> if (exp && context && context[0] == 0)
> if (m == 0)
> nn ();
> }
> ----- CUT ----
> Compile with "-O2 -W -Wall -Werror", there is no warning but once you add
> -fprofile-generate there is an uninitialized warning for context.
> There is a missing jump threading on the trunk which is causing the warning
> to show up.
Started with r12-4790-g4b3a325f07acebf4, may I remove needs-bisection Keyword?
next prev parent reply other threads:[~2022-01-05 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 5:50 [Bug bootstrap/103899] New: " pinskia at gcc dot gnu.org
2022-01-04 6:01 ` [Bug bootstrap/103899] " pinskia at gcc dot gnu.org
2022-01-04 6:05 ` pinskia at gcc dot gnu.org
2022-01-04 6:44 ` pinskia at gcc dot gnu.org
2022-01-05 8:17 ` [Bug tree-optimization/103899] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-05 8:25 ` marxin at gcc dot gnu.org [this message]
2022-01-05 13:55 ` jakub at gcc dot gnu.org
2022-01-05 14:06 ` jakub at gcc dot gnu.org
2022-01-05 21:28 ` pinskia at gcc dot gnu.org
2022-01-06 14:33 ` cvs-commit at gcc dot gnu.org
2022-01-06 14:46 ` jakub at gcc dot gnu.org
2022-01-18 13:56 ` 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-103899-4-kzgdb31HVL@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).