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 tree-optimization/102131] [12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r12-3136
Date: Tue, 25 Jan 2022 01:28:35 +0000 [thread overview]
Message-ID: <bug-102131-4-BNiz645UP8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102131-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102131
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #13 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to CVS Commits from comment #11)
> The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:f1af8528d34418bc874ae9d993ee0dc3559972d2
>
> commit r12-6844-gf1af8528d34418bc874ae9d993ee0dc3559972d2
> Author: Richard Biener <rguenther@suse.de>
> Date: Mon Jan 24 11:50:06 2022 +0100
>
> tree-optimization/102131 - fix niter analysis wrt overflow
>
> This fixes the overflow issues seen with analyzing
> BASE0 + STEP0 cmp BASE1 + STEP1 as BASE0 + STEP0 - STEP1 cmp BASE1
> by following the logic we have when simplifying comparisons.
>
> 2022-01-24 Richard Biener <rguenther@suse.de>
> Jiufu Guo <guojiufu@linux.ibm.com>
>
> PR tree-optimization/100740
> PR tree-optimization/101508
> PR tree-optimization/101972
> PR tree-optimization/102131
> * tree-ssa-loop-niter.cc (number_of_iterations_cond): Properly
> constrain BASE0 + STEP0 cmp BASE1 + STEP1 to
> BASE0 + STEP0 - STEP1 cmp BASE1 transform.
>
> * gcc.dg/torture/pr100740.c: New testcase.
> * gcc.dg/torture/pr101508.c: Likewise.
> * gcc.dg/torture/pr101972.c: Likewise.
> * gcc.dg/torture/pr102131-1.c: Likewise.
> * gcc.dg/torture/pr102131-2.c: Likewise.
> * gcc.dg/torture/pr102131-3.c: Likewise.
> * gcc.dg/torture/pr102131-4.c: Likewise.
It regresses
https://gcc.gnu.org/pipermail/gcc-regression/2022-January/076279.html
prev parent reply other threads:[~2022-01-25 1:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 17:12 [Bug tree-optimization/102131] New: wrong code at -O1 and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2021-08-30 18:13 ` [Bug tree-optimization/102131] [12 Regression] " jakub at gcc dot gnu.org
2021-08-31 6:34 ` guojiufu at gcc dot gnu.org
2021-08-31 9:51 ` guojiufu at gcc dot gnu.org
2021-08-31 10:34 ` amker at gcc dot gnu.org
2021-09-01 9:23 ` guojiufu at gcc dot gnu.org
2021-09-02 7:14 ` guojiufu at gcc dot gnu.org
2021-11-15 17:04 ` [Bug tree-optimization/102131] [12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r12-3136 jakub at gcc dot gnu.org
2021-11-16 2:01 ` guojiufu at gcc dot gnu.org
2021-12-15 10:18 ` zhendong.su at inf dot ethz.ch
2022-01-24 10:43 ` rguenth at gcc dot gnu.org
2022-01-24 12:15 ` cvs-commit at gcc dot gnu.org
2022-01-24 12:48 ` rguenth at gcc dot gnu.org
2022-01-25 1:28 ` crazylht at gmail dot com [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-102131-4-BNiz645UP8@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).