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/96931] [11 Regression] ICE in add_phi_arg, at tree-phinodes.c:359 Date: Fri, 04 Sep 2020 10:23:12 +0000 [thread overview] Message-ID: <bug-96931-4-SNXMJeRG4H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96931-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96931 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:fab77644842869adc8871e133e4c3f4c35b2b245 commit r11-3009-gfab77644842869adc8871e133e4c3f4c35b2b245 Author: Richard Biener <rguenther@suse.de> Date: Fri Sep 4 12:18:38 2020 +0200 tree-optimization/96931 - clear ctrl-altering flag more aggressively The testcase shows that we fail to clear gimple_call_ctrl_altering_p when the last abnormal edge goes away, causing an edge insert to a loop header edge when we have preheaders to split the edge unnecessarily. The following addresses this by more aggressively clearing the flag in cleanup_call_ctrl_altering_flag. 2020-09-04 Richard Biener <rguenther@suse.de> PR tree-optimization/96931 * tree-cfgcleanup.c (cleanup_call_ctrl_altering_flag): If there's a fallthru edge and no abnormal edge the call is no longer control-altering. (cleanup_control_flow_bb): Pass down the BB to cleanup_call_ctrl_altering_flag. * gcc.dg/pr96931.c: New testcase.
next prev parent reply other threads:[~2020-09-04 10:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-04 6:50 [Bug tree-optimization/96931] New: " asolokha at gmx dot com 2020-09-04 7:49 ` [Bug tree-optimization/96931] " rguenth at gcc dot gnu.org 2020-09-04 8:26 ` rguenth at gcc dot gnu.org 2020-09-04 8:34 ` rguenth at gcc dot gnu.org 2020-09-04 10:23 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-04 10:23 ` rguenth 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-96931-4-SNXMJeRG4H@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: linkBe 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).