public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98117] [8/9/10 Regression] wrong code with "-O3 -fno-tree-scev-cprop" since r8-1163-g7078979b291419f3
Date: Mon, 11 Jan 2021 14:10:59 +0000 [thread overview]
Message-ID: <bug-98117-4-Nbcek6OxXj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98117-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98117
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:69894ce172412996c10c89838717980ede7c9003
commit r10-9247-g69894ce172412996c10c89838717980ede7c9003
Author: Richard Biener <rguenther@suse.de>
Date: Mon Dec 7 10:29:07 2020 +0100
tree-optimization/98117 - fix range set by vectorization on niter IVs
This avoids the degenerate case of a TYPE_MAX_VALUE latch iteration
count value causing wrong range info for the vector IV. There's
still the case of VF == 1 where if we don't know whether we hit the
above case we cannot emit a range.
2020-12-07 Richard Biener <rguenther@suse.de>
PR tree-optimization/98117
* tree-vect-loop-manip.c (vect_gen_vector_loop_niters):
Properly handle degenerate niter when setting the vector
loop IV range.
* gcc.dg/torture/pr98117.c: New testcase.
(cherry picked from commit cdcbef3c3310a14f2994982b44cb1f8e14c77232)
next prev parent reply other threads:[~2021-01-11 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:31 [Bug tree-optimization/98117] New: wrong code with "-O3 -fno-tree-scev-cprop" suochenyao at 163 dot com
2020-12-03 11:51 ` [Bug tree-optimization/98117] [8/9/10/11 Regression] wrong code with "-O3 -fno-tree-scev-cprop" since r8-1163-g7078979b291419f3 marxin at gcc dot gnu.org
2020-12-03 12:30 ` rguenth at gcc dot gnu.org
2020-12-07 8:39 ` rguenth at gcc dot gnu.org
2020-12-07 8:51 ` rguenth at gcc dot gnu.org
2020-12-07 9:27 ` rguenth at gcc dot gnu.org
2020-12-07 11:06 ` cvs-commit at gcc dot gnu.org
2020-12-07 11:06 ` [Bug tree-optimization/98117] [8/9/10 " rguenth at gcc dot gnu.org
2021-01-11 14:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-17 9:35 ` [Bug tree-optimization/98117] [8/9 " cvs-commit at gcc dot gnu.org
2021-04-26 10:46 ` [Bug tree-optimization/98117] [8 " cvs-commit at gcc dot gnu.org
2021-04-26 10:49 ` 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-98117-4-Nbcek6OxXj@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).