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 rtl-optimization/99085] [10 Regression] ICE: verify_flow_info failed (error: multiple hot/cold transitions found) Date: Fri, 19 Mar 2021 23:30:00 +0000 [thread overview] Message-ID: <bug-99085-4-uH0awt6pG6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99085-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99085 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:a7c4a70077ad7291f57663aef62d097018d28a10 commit r10-9478-ga7c4a70077ad7291f57663aef62d097018d28a10 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Mar 3 09:51:54 2021 +0100 cfgrtl: Fix up fixup_partitions caused ICE [PR99085] fixup_partitions sometimes changes some basic blocks from hot partition to cold partition, in particular if after unreachable block removal or other optimizations a hot partition block is dominated by cold partition block(s). It fixes up the edges and jumps on those edges, but when after reorder blocks and in rtl (non-cfglayout) mode that is clearly not enough, because it keeps the block order the same and so we can end up with more than 1 hot/cold section transition in the same function. So, this patch fixes that up too. 2021-03-03 Jakub Jelinek <jakub@redhat.com> PR target/99085 * cfgrtl.c (fixup_partitions): When changing some bbs from hot to cold partitions, if in non-layout mode after reorder_blocks also move affected blocks to ensure a single partition transition. * gcc.dg/graphite/pr99085.c: New test. (cherry picked from commit 4ad5b1915d50cc39691487f58794d699c7900ace)
next prev parent reply other threads:[~2021-03-19 23:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-13 7:59 [Bug rtl-optimization/99085] New: [11 " asolokha at gmx dot com 2021-02-15 8:23 ` [Bug rtl-optimization/99085] " rguenth at gcc dot gnu.org 2021-02-15 8:29 ` [Bug rtl-optimization/99085] [10/11 " jakub at gcc dot gnu.org 2021-02-15 8:30 ` jakub at gcc dot gnu.org 2021-02-15 16:11 ` jakub at gcc dot gnu.org 2021-03-03 8:52 ` cvs-commit at gcc dot gnu.org 2021-03-03 8:57 ` [Bug rtl-optimization/99085] [10 " jakub at gcc dot gnu.org 2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-20 8:08 ` jakub 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-99085-4-uH0awt6pG6@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).