public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta by r9-2475
Date: Sun, 17 Oct 2021 00:53:36 +0000 [thread overview]
Message-ID: <bug-102798-4-gqIhvNCn3s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102798-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102798
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at gcc dot gnu.org
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
Looks like a VRP bug. For:
<bb 2> [local count: 168730857]:
if (in_16(D) != 0B)
goto <bb 3>; [70.00%]
else
goto <bb 6>; [30.00%]
<bb 3> [local count: 118111600]:
_1 = size_17(D) + 18446744073709551615;
out_26 = out_18(D) + _1;
goto <bb 5>; [100.00%]
VRP reports:
in_16(D) : BACK visiting block 3 for in_16(D)
2->3 has cache, const unsigned char * VARYING, update.
FWD visiting block 3 for in_16(D) starting range : UNDEFINED
edge 2->3 :const unsigned char * [1B, +INF]
Updating range to const unsigned char * [1B, +INF]
Updating blocks :
DONE visiting blocks for in_16(D)
next prev parent reply other threads:[~2021-10-17 0:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 12:43 [Bug target/102798] New: [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f zsojka at seznam dot cz
2021-10-16 15:54 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f by r9-2475 hjl.tools at gmail dot com
2021-10-16 16:31 ` hjl.tools at gmail dot com
2021-10-16 18:10 ` hjl.tools at gmail dot com
2021-10-16 18:16 ` hjl.tools at gmail dot com
2021-10-16 18:42 ` pinskia at gcc dot gnu.org
2021-10-16 18:43 ` pinskia at gcc dot gnu.org
2021-10-16 18:46 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta " pinskia at gcc dot gnu.org
2021-10-16 19:08 ` hjl.tools at gmail dot com
2021-10-17 0:53 ` hjl.tools at gmail dot com [this message]
2021-10-17 2:49 ` hjl.tools at gmail dot com
2021-10-17 13:33 ` hjl.tools at gmail dot com
2021-10-17 18:29 ` hjl.tools at gmail dot com
2021-10-18 6:39 ` rguenth at gcc dot gnu.org
2021-10-18 7:03 ` rguenth at gcc dot gnu.org
2021-10-18 8:26 ` cvs-commit at gcc dot gnu.org
2021-10-18 8:27 ` [Bug tree-optimization/102798] [9/10/11 " rguenth at gcc dot gnu.org
2021-11-08 13:32 ` cvs-commit at gcc dot gnu.org
2022-02-17 10:48 ` [Bug tree-optimization/102798] [9/10 " cvs-commit at gcc dot gnu.org
2022-02-17 11:57 ` [Bug tree-optimization/102798] [9 " cvs-commit at gcc dot gnu.org
2022-02-17 11:58 ` rguenth at gcc dot gnu.org
2022-02-18 7:10 ` rguenth at gcc dot gnu.org
2022-02-18 7:11 ` rguenth at gcc dot gnu.org
2022-02-18 7:13 ` rguenth at gcc dot gnu.org
2022-02-18 8:21 ` rguenth at gcc dot gnu.org
2022-02-18 8:22 ` 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-102798-4-gqIhvNCn3s@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).