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/104530] [12/13 Regression] Dead Code Elimination Regression at -O3 (trunk vs. 11.2.0)
Date: Tue, 08 Nov 2022 00:22:45 +0000	[thread overview]
Message-ID: <bug-104530-4-WdG60BqIfW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104530-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 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:c838119946c9f75f1e42f4320275355822cc86fc

commit r13-3765-gc838119946c9f75f1e42f4320275355822cc86fc
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Nov 7 15:07:35 2022 -0500

    Add transitive inferred range processing.

    Rewalk statements at the end of a block to see if any inferred ranges
    affect earlier calculations and register those as inferred ranges.

            gcc/
            PR tree-optimization/104530
            * gimple-range-cache.cc (ranger_cache::register_inferred_value):
            New.  Split from:
            (ranger_cache::apply_inferred_ranges): Move setting cache to
            separate function.
            * gimple-range-cache.h (register_inferred_value): New prototype.
            * gimple-range-infer.cc (infer_range_manager::has_range_p): New.
            * gimple-range-infer.h (has_range_p): New prototype.
            * gimple-range.cc (register_transitive_inferred_ranges): New.
            * gimple-range.h (register_transitive_inferred_ranges): New proto.
            * tree-vrp.cc (rvrp_folder::fold_stmt): Check for transitive
inferred
            ranges at the end of the block before folding final stmt.

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

  parent reply	other threads:[~2022-11-08  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 16:40 [Bug tree-optimization/104530] New: [12 " theodort at inf dot ethz.ch
2022-02-14 16:47 ` [Bug tree-optimization/104530] " jakub at gcc dot gnu.org
2022-02-15 23:14 ` amacleod at redhat dot com
2022-02-21 13:10 ` jakub at gcc dot gnu.org
2022-04-19 15:36 ` rguenth at gcc dot gnu.org
2022-05-06  8:32 ` [Bug tree-optimization/104530] [12/13 " jakub at gcc dot gnu.org
2022-11-08  0:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-08  0:23 ` 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-104530-4-WdG60BqIfW@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).