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

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

--- Comment #4 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:e15425e899e4a9eec768cf74aaf36cdbf1d29913

commit r12-7253-ge15425e899e4a9eec768cf74aaf36cdbf1d29913
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Feb 14 19:43:40 2022 -0500

    Use GORI to evaluate arguments of a COND_EXPR.

    Provide an API into gori to perform a basic evaluation of the arguments of
a
    COND_EXPR if they are in the dependency chain of the condition.

            PR tree-optimization/104526
            gcc/
            * gimple-range-fold.cc (fold_using_range::range_of_cond_expr): Call
            new routine.
            * gimple-range-gori.cc (range_def_chain::get_def_chain): Force a
build
            of dependency chain if there isn't one.
            (gori_compute::condexpr_adjust): New.
            * gimple-range-gori.h (class gori_compute): New prototype.

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

  parent reply	other threads:[~2022-02-15 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 10:07 [Bug tree-optimization/104526] New: " theodort at inf dot ethz.ch
2022-02-14 10:12 ` [Bug tree-optimization/104526] " rguenth at gcc dot gnu.org
2022-02-14 13:41 ` jakub at gcc dot gnu.org
2022-02-14 14:33 ` jakub at gcc dot gnu.org
2022-02-14 22:14 ` amacleod at redhat dot com
2022-02-15 22:12 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-15 22:13 ` amacleod at redhat dot com
2022-02-16 12:39 ` jakub at gcc dot gnu.org
2022-02-16 14:05 ` amacleod at redhat dot com
2022-02-16 14:07 ` jakub 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-104526-4-i7NId131bV@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).