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 09:11:09 +0000 [thread overview] Message-ID: <bug-108738-4-z1cw67hImy@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-02-09 Ever confirmed|0 |1 Known to fail| |10.4.0 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Happens at least since GCC 10. There's a comment already: /* ??? The following is quadratic since analyze_register_chain iterates over all refs to look for dual-mode regs. Instead this should be done separately for all regs mentioned in the chain once. */ df_ref ref; for (ref = DF_INSN_UID_DEFS (insn_uid); ref; ref = DF_REF_NEXT_LOC (ref)) if (!HARD_REGISTER_P (DF_REF_REG (ref))) analyze_register_chain (candidates, ref); but the walk also adds to the queue, so it's more interwinded and the suggested solution isn't the proper. Instead it might be possible to just record already visited regs.
next prev parent reply other threads:[~2023-02-09 9:11 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 [this message] 2023-02-09 9:24 ` rguenth at gcc dot gnu.org 2023-02-09 12:48 ` rguenth at gcc dot gnu.org 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-z1cw67hImy@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).