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/98513] [10 Regression] Wrong code with -O3 since r10-2804-gbf05a3bbb58b3558
Date: Tue, 12 Jan 2021 15:23:51 +0000	[thread overview]
Message-ID: <bug-98513-4-YBIKzLs3iW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98513-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98513

--- Comment #14 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:71878c08e967997b570b1acbd9ffef4234e94698

commit r10-9263-g71878c08e967997b570b1acbd9ffef4234e94698
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jan 6 09:26:55 2021 +0100

    tree-optimization/98513 - fix bug in range intersection code

    This fixes a premature optimization in the range intersection code
    which assumes earlier branches have to be taken, not taking into
    account that for symbolic ranges we cannot always compare endpoints.
    The fix is to instantiate the compare deemed redundant (which then
    fails as undecidable for the testcase).

    2021-01-06  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/98513
            * value-range.cc (intersect_ranges): Compare the upper bounds
            for the expected relation.

            * gcc.dg/tree-ssa/pr98513.c: New testcase.

    (cherry picked from commit a05cc70a6c1ae0e5b22e16f4d8d13995a38ea1f9)

  parent reply	other threads:[~2021-01-12 15:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 15:21 [Bug tree-optimization/98513] New: [10/11 " marxin at gcc dot gnu.org
2021-01-04 15:21 ` [Bug tree-optimization/98513] " marxin at gcc dot gnu.org
2021-01-04 15:41 ` marxin at gcc dot gnu.org
2021-01-04 16:24 ` marxin at gcc dot gnu.org
2021-01-04 16:33 ` marxin at gcc dot gnu.org
2021-01-05  9:21 ` marxin at gcc dot gnu.org
2021-01-05  9:24 ` marxin at gcc dot gnu.org
2021-01-05  9:28 ` marxin at gcc dot gnu.org
2021-01-05  9:28 ` rguenth at gcc dot gnu.org
2021-01-05 15:55 ` amacleod at redhat dot com
2021-01-05 16:04 ` rguenth at gcc dot gnu.org
2021-01-05 16:40 ` rguenth at gcc dot gnu.org
2021-01-06  8:02 ` rguenth at gcc dot gnu.org
2021-01-06  8:26 ` rguenth at gcc dot gnu.org
2021-01-06  9:21 ` cvs-commit at gcc dot gnu.org
2021-01-06  9:33 ` [Bug tree-optimization/98513] [10 " marxin at gcc dot gnu.org
2021-01-12 15:23 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-12 15:26 ` rguenth at gcc dot gnu.org
2021-10-06 22:34 ` pinskia 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-98513-4-YBIKzLs3iW@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).