public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98514] ICE in insert_operand_rank Date: Tue, 05 Jan 2021 11:28:00 +0000 [thread overview] Message-ID: <bug-98514-4-nqTm5f3zzV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98514-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98514 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- note the BB rank assignment via ++rank << 16 implies no more than 1 << 15 SSA defs in each BB as well. It would be better to simply assign the BB rank while traversing the IL in a DFS walk (SSA names pick up rank from their defs or the BB rank of their def) where we know how to assign a distinct rank for the BB. But yes, a HWI for the rank looks sensible (or int64_t - HWI is some legacy thing and 'rank' isn't tied to any struct using HWIs)
next prev parent reply other threads:[~2021-01-05 11:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 15:58 [Bug tree-optimization/98514] New: " jakub at gcc dot gnu.org 2021-01-04 16:12 ` [Bug tree-optimization/98514] " jakub at gcc dot gnu.org 2021-01-04 16:33 ` jakub at gcc dot gnu.org 2021-01-05 11:28 ` rguenth at gcc dot gnu.org [this message] 2021-01-05 15:38 ` cvs-commit at gcc dot gnu.org 2021-01-05 15:39 ` jakub at gcc dot gnu.org 2021-01-06 9:40 ` cvs-commit at gcc dot gnu.org 2021-01-29 10:39 ` 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-98514-4-nqTm5f3zzV@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).