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/101496] [12 Regression] ice during GIMPLE pass: evrp
Date: Thu, 22 Jul 2021 12:53:04 +0000	[thread overview]
Message-ID: <bug-101496-4-9K3ZvyN2pk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101496-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:e58093276a6e319c2a6d9f02e343fbf8400dab60

commit r12-2464-ge58093276a6e319c2a6d9f02e343fbf8400dab60
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Jul 19 14:02:57 2021 -0400

    Only call vrp_visit_cond_stmt if range_of_stmt doesn't resolve to a const.

    Eevntually all functionality will be subsumed.  Until then, call it only
    if needed.

            gcc/
            PR tree-optimization/101496
            * vr-values.c (simplify_using_ranges::fold_cond): Call
range_of_stmt
            first, then vrp_visit_cond_Stmt.

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

  parent reply	other threads:[~2021-07-22 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18  7:42 [Bug c/101496] New: " dcb314 at hotmail dot com
2021-07-18  7:51 ` [Bug tree-optimization/101496] [12 Regression] " pinskia at gcc dot gnu.org
2021-07-18  7:53 ` pinskia at gcc dot gnu.org
2021-07-18  9:12 ` dcb314 at hotmail dot com
2021-07-18  9:44 ` dcb314 at hotmail dot com
2021-07-18  9:59 ` dcb314 at hotmail dot com
2021-07-18 10:28 ` dcb314 at hotmail dot com
2021-07-19  6:36 ` rguenth at gcc dot gnu.org
2021-07-19 18:44 ` amacleod at redhat dot com
2021-07-22 12:53 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-22 13:07 ` 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-101496-4-9K3ZvyN2pk@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).