public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107197] valgrind error in function same_line_p during build
Date: Mon, 10 Oct 2022 08:32:22 +0000 [thread overview]
Message-ID: <bug-107197-4-dyJoPHJHet@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107197-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107197
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #7)
> (In reply to Richard Biener from comment #5)
> > Probably the same as PR107193
>
> I guess so, see comment3 in PR107193.
It looks like exact below warns for.
==107792== Conditional jump or move depends on uninitialised value(s)
==107792== at 0xD5004B: same_line_p (tree-cfg.cc:1160)
==107792== by 0xD5004B: assign_discriminators (tree-cfg.cc:1224)
==107792== by 0xD5004B: build_gimple_cfg (tree-cfg.cc:251)
==107792== by 0xD5004B: execute_build_cfg (tree-cfg.cc:371)
next prev parent reply other threads:[~2022-10-10 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 19:32 [Bug c/107197] New: " dcb314 at hotmail dot com
2022-10-09 19:49 ` [Bug c/107197] " dcb314 at hotmail dot com
2022-10-09 20:28 ` dcb314 at hotmail dot com
2022-10-09 20:33 ` dcb314 at hotmail dot com
2022-10-10 7:03 ` dcb314 at hotmail dot com
2022-10-10 7:26 ` rguenth at gcc dot gnu.org
2022-10-10 8:13 ` dcb314 at hotmail dot com
2022-10-10 8:31 ` crazylht at gmail dot com
2022-10-10 8:32 ` crazylht at gmail dot com [this message]
2022-10-11 19:58 ` erozen at microsoft dot com
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-107197-4-dyJoPHJHet@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).