public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66678] loop counter not accurately described by vrp
Date: Thu, 10 Aug 2023 06:57:15 +0000 [thread overview]
Message-ID: <bug-66678-4-2wvXP0maYj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66678
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Aug 2023, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66678
>
> --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> So in GCC 12+ after evrp
> # RANGE [0, 4294967294] NONZERO 4294967295
> _1 = (long unsigned intD.16) i_9;
> # RANGE [0, 17179869176] NONZERO 17179869180
> _2 = _1 * 4;
> ...
> # RANGE [1, 4294967295]
> i_17 = i_9 + 1;
>
> So maybe this has been fix ...
Note with ranger there's a regression WRT loop IVs not handled by
SCEV because it no longer iterates.
prev parent reply other threads:[~2023-08-10 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:15 [Bug tree-optimization/66678] New: " vries at gcc dot gnu.org
2015-06-26 12:53 ` [Bug tree-optimization/66678] " vries at gcc dot gnu.org
2015-06-30 8:32 ` vries at gcc dot gnu.org
2015-06-30 8:48 ` rguenth at gcc dot gnu.org
2023-08-09 23:06 ` pinskia at gcc dot gnu.org
2023-08-10 6:57 ` rguenther at suse dot de [this message]
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-66678-4-2wvXP0maYj@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).