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/50107] [IRA, i386] allocates regiters in very non-optimal way Date: Wed, 17 Aug 2011 17:19:00 -0000 [thread overview] Message-ID: <bug-50107-4-SQvdj2eV3V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50107-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50107 --- Comment #2 from Vladimir Makarov <vmakarov at redhat dot com> 2011-08-17 17:16:11 UTC --- I guess something wrong with hard register preferencing for multi-register pseudos in ira-color.c::ira_assign. I believe it works fine for one-register pseudos. I'll look at this. Thanks for reporting. By the way, your patch is wrong. There should be TARGET_64BIT in define_split instead of !TARGET_64BIT.
next prev parent reply other threads:[~2011-08-17 17:17 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-17 13:42 [Bug rtl-optimization/50107] New: " kirill.yukhin at intel dot com 2011-08-17 13:53 ` [Bug rtl-optimization/50107] " kirill.yukhin at intel dot com 2011-08-17 17:19 ` vmakarov at redhat dot com [this message] 2011-08-17 18:58 ` hjl.tools at gmail dot com 2011-08-17 19:18 ` hjl.tools at gmail dot com 2011-08-17 19:32 ` hjl.tools at gmail dot com 2011-08-17 22:29 ` vmakarov at redhat dot com 2011-08-18 14:55 ` hjl.tools at gmail dot com 2011-08-18 15:03 ` vmakarov at gcc dot gnu.org 2011-08-18 15:31 ` hjl.tools at gmail dot com 2011-08-18 18:29 ` vmakarov at redhat dot com 2011-08-18 19:02 ` hjl.tools at gmail dot com 2011-08-19 6:05 ` [Bug rtl-optimization/50107] [IRA, i386] allocates registers " hjl.tools at gmail dot com 2011-08-19 16:14 ` hjl.tools at gmail dot com 2011-08-19 16:24 ` vmakarov at redhat dot com 2021-12-26 22:18 ` pinskia 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-50107-4-SQvdj2eV3V@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).