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 ipa/96806] ICE: in good_cloning_opportunity_p, at ipa-cp.c:3235 with -O -fipa-cp -fipa-cp-clone --param=ipa-cp-max-recursive-depth=94 --param=logical-op-non-short-circuit=0
Date: Mon, 31 Aug 2020 08:35:09 +0000	[thread overview]
Message-ID: <bug-96806-4-1QcFF2L3KK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96806-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Feng Xue <fxue@gcc.gnu.org>:

https://gcc.gnu.org/g:e11c4b7f837bc6b4c22b1f5bf41a9d0608d256be

commit r11-2945-ge11c4b7f837bc6b4c22b1f5bf41a9d0608d256be
Author: Feng Xue <fxue@os.amperecomputing.com>
Date:   Mon Aug 31 15:00:52 2020 +0800

    ipa/96806 - Fix ICE in ipa-cp due to integer addition overflow

    2020-08-31  Feng Xue  <fxue@os.amperecomputing.com>

    gcc/
            PR tree-optimization/96806
            * ipa-cp.c (decide_about_value): Use safe_add to avoid cost
addition
            overflow.

    gcc/testsuite/
            PR tree-optimization/96806
            * g++.dg/ipa/pr96806.C: New test.

  parent reply	other threads:[~2020-08-31  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 19:48 [Bug ipa/96806] New: " zsojka at seznam dot cz
2020-08-26 20:14 ` [Bug ipa/96806] " marxin at gcc dot gnu.org
2020-08-31  8:35 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-26  6:33 ` 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-96806-4-1QcFF2L3KK@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).