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 middle-end/99694] [9 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7
Date: Mon, 12 Apr 2021 11:23:49 +0000 [thread overview]
Message-ID: <bug-99694-4-0A6HtPrd6z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99694-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:a343b3bda748c2eb602d4e7de17d827a5912c53b
commit r9-9343-ga343b3bda748c2eb602d4e7de17d827a5912c53b
Author: Richard Biener <rguenther@suse.de>
Date: Mon Mar 22 11:09:46 2021 +0100
tree-optimization/99694 - fix value-numbering PHIs
This avoids endless cycling when a PHI node with unchanged backedge
value (the PHI result appearing there) is subject to CSE since doing
that effectively alters the hash entry. The way to avoid this is
to ignore such edges when processing the PHI node.
2021-03-22 Richard Biener <rguenther@suse.de>
PR tree-optimization/99694
* tree-ssa-sccvn.c (visit_phi): Ignore edges with the
PHI result.
* gcc.dg/torture/pr99694.c: New testcase.
(cherry picked from commit b931e4792b8696f3da69f70988720c4d1ec6142a)
next prev parent reply other threads:[~2021-04-12 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 13:48 [Bug c/99694] New: gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os haoxintu at gmail dot com
2021-03-22 8:14 ` [Bug middle-end/99694] [9/10/11 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7 marxin at gcc dot gnu.org
2021-03-22 8:32 ` jakub at gcc dot gnu.org
2021-03-22 9:05 ` rguenth at gcc dot gnu.org
2021-03-22 13:37 ` cvs-commit at gcc dot gnu.org
2021-03-22 13:38 ` [Bug middle-end/99694] [9/10 " rguenth at gcc dot gnu.org
2021-03-24 14:26 ` cvs-commit at gcc dot gnu.org
2021-03-28 3:27 ` [Bug middle-end/99694] [9 " haoxintu at gmail dot com
2021-03-30 7:31 ` marxin at gcc dot gnu.org
2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-12 11:24 ` rguenth at gcc dot gnu.org
2021-08-04 8:31 ` haoxintu at gmail dot com
2021-08-04 8:45 ` marxin at gcc dot gnu.org
2021-08-04 8:50 ` haoxintu at gmail dot com
2021-08-04 11:37 ` rguenth at gcc dot gnu.org
2021-08-04 11:51 ` jakub at gcc dot gnu.org
2021-08-04 12:42 ` marxin at gcc dot gnu.org
2021-08-04 13:19 ` haoxintu at gmail 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-99694-4-0A6HtPrd6z@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).