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 target/108738] compile-time and memory-hog in mdreorg Date: Thu, 09 Feb 2023 12:48:39 +0000 [thread overview] Message-ID: <bug-108738-4-kgWwMFFQ36@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108738-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- The odd thing is that DF_REF_CHAIN of a USE ref contains _all_ definitions of the pseudo while DF_REF_CHAIN of a DEF ref contains only reaching uses!? Probably an artifact of how df_chain_create_bb_process_use operates. That makes this much harder to fix ...
next prev parent reply other threads:[~2023-02-09 12:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 8:10 [Bug target/108738] New: " rguenth at gcc dot gnu.org 2023-02-09 8:47 ` [Bug target/108738] " rguenth at gcc dot gnu.org 2023-02-09 9:11 ` rguenth at gcc dot gnu.org 2023-02-09 9:24 ` rguenth at gcc dot gnu.org 2023-02-09 12:48 ` rguenth at gcc dot gnu.org [this message] 2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org 2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org 2023-03-02 11:38 ` rguenth at gcc dot gnu.org 2023-03-03 7:31 ` cvs-commit at gcc dot gnu.org 2023-03-03 7:33 ` 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-108738-4-kgWwMFFQ36@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).