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 other/50775] Register allocator sets up frame and frame pointer with low register pressure
Date: Sun, 04 Dec 2011 04:09:00 -0000 [thread overview]
Message-ID: <bug-50775-4-WSBsuNnWZB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50775-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50775
--- Comment #6 from Vladimir Makarov <vmakarov at redhat dot com> 2011-12-04 04:09:06 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
>
> > Wrong profitable hard regs calculation for register files requiring aligned
> > start register was a merging problem with a patch for allocation without cover
> > classes.
> >
> > I'll try make a patch this week to solve the problem.
>
> Thanks you are taking care of this. Will it also improve the situation for
> 3-byte types as introduced in PR50931? 3-byte types also start in even
> registers.
I think it will improve.
Sorry for the delay with the patch. The changes are big (the patch is about
1700 lines long) so I need a thorough testing.
next prev parent reply other threads:[~2011-12-04 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 11:44 [Bug other/50775] New: " gjl at gcc dot gnu.org
2011-10-18 12:08 ` [Bug other/50775] " gjl at gcc dot gnu.org
2011-10-25 9:48 ` gjl at gcc dot gnu.org
2011-11-15 16:43 ` denisc at gcc dot gnu.org
2011-11-15 16:49 ` denisc at gcc dot gnu.org
2011-11-28 22:10 ` vmakarov at redhat dot com
2011-11-29 0:16 ` gjl at gcc dot gnu.org
2011-12-04 4:09 ` vmakarov at redhat dot com [this message]
2011-12-05 17:03 ` vmakarov at gcc dot gnu.org
2011-12-05 18:16 ` law at redhat dot com
2011-12-15 19:10 ` gjl 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-50775-4-WSBsuNnWZB@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: link
Be 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).