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/108356] [13 Regression] Dead Code Elimination Regression at -O2 since r13-434-g6b156044c12bc4
Date: Wed, 01 Feb 2023 14:27:20 +0000	[thread overview]
Message-ID: <bug-108356-4-rxA6AJtYuM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108356-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:

https://gcc.gnu.org/g:881bf8de9b07fb501d61ade8f521f1cc9dbe712e

commit r13-5630-g881bf8de9b07fb501d61ade8f521f1cc9dbe712e
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Tue Jan 10 13:40:56 2023 -0500

    Ranger cache - always use range_from_dom when updating.

    When updating an existing range, if we dont query the dom tree, we can
    get the global range instead of a proper range on some incoming edges
    which cause the range to not be refined properly.

            PR tree-optimization/108356
            gcc/
            * gimple-range-cache.cc (ranger_cache::range_on_edge): Always
            do a search of the DOM tree for a range.

            gcc/testsuite/
            * gcc.dg/pr108356.c: New.

  parent reply	other threads:[~2023-02-01 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 12:50 [Bug tree-optimization/108356] New: Dead Code Elimination Regression at -O2 (trunk vs. 12.2.0) yann at ywg dot ch
2023-01-10 14:45 ` [Bug tree-optimization/108356] [13 Regression] Dead Code Elimination Regression at -O2 since r13-434-g6b156044c12bc4 marxin at gcc dot gnu.org
2023-01-10 16:16 ` amacleod at redhat dot com
2023-01-10 16:26 ` rguenth at gcc dot gnu.org
2023-01-10 16:55 ` amacleod at redhat dot com
2023-01-13 21:37 ` amacleod at redhat dot com
2023-01-13 22:23 ` amacleod at redhat dot com
2023-02-01 14:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-01 14:27 ` amacleod at redhat dot com

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-108356-4-rxA6AJtYuM@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).