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/96491] [11 Regression] ICE: tree check: expected ssa_name, have integer_cst in add_phi_arg, at tree-phinodes.c:373 Date: Thu, 06 Aug 2020 10:20:49 +0000 [thread overview] Message-ID: <bug-96491-4-HL6t6btFa5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96491 --- Comment #2 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:89b84cd794f984038984c10b03c3b0ab582f49cc commit r11-2591-g89b84cd794f984038984c10b03c3b0ab582f49cc Author: Richard Biener <rguenther@suse.de> Date: Thu Aug 6 12:18:24 2020 +0200 tree-optimization/96491 - avoid store commoning across abnormal edges This avoids store commoning across abnormal edges since that easily can disrupt abnormal coalescing because it might create overlapping lifetime of variables. 2020-08-06 Richard Biener <rguenther@suse.de> PR tree-optimization/96491 * tree-ssa-sink.c (sink_common_stores_to_bb): Avoid sinking across abnormal edges. * gcc.dg/torture/pr96491.c: New testcase.
next prev parent reply other threads:[~2020-08-06 10:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-06 2:40 [Bug tree-optimization/96491] New: " asolokha at gmx dot com 2020-08-06 8:03 ` [Bug tree-optimization/96491] " rguenth at gcc dot gnu.org 2020-08-06 10:20 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-06 10:25 ` 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-96491-4-HL6t6btFa5@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).