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/100600] [11/12 Regression] ICE: in verify_hash_value, at fold-const.c:3929 since r11-5206-gd1081010a1addfcf
Date: Mon, 16 Aug 2021 07:53:30 +0000	[thread overview]
Message-ID: <bug-100600-4-95MQyfxatP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100600-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

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

commit r12-2920-gb0de3ad2620d665ab481c2f24204f77f386ff6b2
Author: Martin Liska <mliska@suse.cz>
Date:   Fri Aug 13 12:35:47 2021 +0200

    ipa: ICF should check SSA_NAME_IS_DEFAULT_DEF

            PR ipa/100600

    gcc/ChangeLog:

            * ipa-icf-gimple.c (func_checker::compare_ssa_name): Do not
              consider equal SSA_NAMEs when one is a param.

    gcc/testsuite/ChangeLog:

            * gcc.dg/ipa/pr100600.c: New test.

  parent reply	other threads:[~2021-08-16  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 14:31 [Bug c/100600] New: ICE: in verify_hash_value, at fold-const.c:3929 cnsun at uwaterloo dot ca
2021-05-17  7:53 ` [Bug ipa/100600] [11/12 Regression] ICE: in verify_hash_value, at fold-const.c:3929 since r11-5206-gd1081010a1addfcf marxin at gcc dot gnu.org
2021-05-17 12:17 ` rguenth at gcc dot gnu.org
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2021-08-16  7:53 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-16  7:54 ` [Bug ipa/100600] [11 " marxin at gcc dot gnu.org
2021-08-16 11:14 ` cvs-commit at gcc dot gnu.org
2021-08-16 11:17 ` marxin 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-100600-4-95MQyfxatP@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).