public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57462] ira-costs considers only a single register at a time Date: Fri, 31 May 2013 13:55:00 -0000 [thread overview] Message-ID: <bug-57462-4-AKFLUHMiFH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57462-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57462 Vladimir Makarov <vmakarov at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at redhat dot com --- Comment #1 from Vladimir Makarov <vmakarov at redhat dot com> --- Thanks for the analysis. That would be an interesting problem to solve. Although I don't know when I could start work on the problem. The code you are mentioning is actually adaptation of code from old regclass pass which existed since day 1 of GCC. The optimal solution of the problem might be NP-complete (I am not sure about it, but at least long time ago I tried to describe it by ILP). I should say that even the current cost code is very expensive and speeding up is on my list to do. Better solution (through better heuristics) probably will be even more expensive. IMHO, it is also GCC specific problem because GCC postpones code selection (usually compilers do complete code selection before RA, e.g. selecting insn for add in this case) and that is a consequence of GCC machine description model. Doing complete code selection before RA is also challenging task. In any case, the problem is known and quite interesting. There are a lot of different approaches to solve it (some require even GCC architectural changes), none of them are easy. So I don't think, the problem will be solved soon. Sorry.
next parent reply other threads:[~2013-05-31 13:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-57462-4@http.gcc.gnu.org/bugzilla/> 2013-05-31 13:55 ` vmakarov at redhat dot com [this message] 2013-06-03 21:18 ` josh.m.conner at gmail dot com 2013-07-10 22:10 ` ramana at gcc dot gnu.org 2015-01-23 10:32 ` ramana 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-57462-4-AKFLUHMiFH@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).