From: Steven Bosscher <stevenb@suse.de>
To: gcc@gcc.gnu.org
Cc: Peter Bergner <bergner@vnet.ibm.com>,
Andrew MacLeod <amacleod@redhat.com>,
Daniel Berlin <dberlin@dberlin.org>
Subject: Re: Register Allocation
Date: Tue, 22 Nov 2005 21:55:00 -0000 [thread overview]
Message-ID: <200511222256.13823.stevenb@suse.de> (raw)
In-Reply-To: <1132687596.7748.32.camel@otta.rchland.ibm.com>
On Tuesday 22 November 2005 20:26, Peter Bergner wrote:
> Insn Annotations [page(s) 17-18]:
> * I like the idea of easy access to the register usage info
> provided by the insn annotations. RTL isn't really setup
> for making that easy.
But it is if you use df.c. Really, it is. It is right there:
reg-use and reg-def chains per insn, UD and DU chains, etc.
> Spill Cost Engine [page(s) 26-29]:
> * The register allocator should not be estimating the execution
> frequency of a basic block as 10^nesting level. That information
> should be coming from the cfg which comes from profile data or
> from a good static profile.
The profile information or branch predictions are available in the
CFG. In fact, even the current Chow-like allocator uses it. See
allocno_compare in global.c.
Gr.
Steven
next prev parent reply other threads:[~2005-11-22 21:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 16:53 Andrew MacLeod
2005-11-18 2:55 ` Mark Mitchell
2005-11-18 3:27 ` Daniel Jacobowitz
2005-11-18 9:53 ` Giovanni Bajo
2005-11-18 15:28 ` Andrew MacLeod
2005-11-19 19:31 ` Ian Lance Taylor
2005-11-19 20:20 ` Denis Chertykov
2005-11-20 0:20 ` Giovanni Bajo
2005-11-23 17:07 ` Andrew MacLeod
2005-11-23 20:43 ` Ian Lance Taylor
2005-11-20 0:37 ` Steven Bosscher
2005-11-23 17:08 ` Andrew MacLeod
2005-11-22 19:26 ` Peter Bergner
2005-11-22 21:55 ` Steven Bosscher [this message]
[not found] ` <200511222256.13823.>
2005-11-22 22:58 ` Peter Bergner
2005-11-23 14:06 ` Michael Matz
2005-11-23 20:50 ` Peter Bergner
2005-11-23 17:08 ` Andrew MacLeod
-- strict thread matches above, loose matches on Subject: below --
2010-12-23 8:13 register allocation roy rosen
2010-12-23 16:48 ` Vladimir Makarov
2010-12-23 17:22 ` Jeff Law
2010-12-27 15:43 ` roy rosen
2011-01-03 15:41 ` Jeff Law
2011-01-05 14:44 ` roy rosen
2011-01-05 15:26 ` Jeff Law
2011-01-11 16:11 ` Vladimir Makarov
2011-01-11 15:53 ` Vladimir Makarov
2005-11-24 20:51 Register Allocation Joern RENNECKE
2004-09-22 1:21 Adrian Strätling
2004-09-22 5:22 ` tm_gccmail
2004-10-04 14:13 ` Nick Ing-Simmons
2004-05-02 13:27 register allocation Qiong Cai
2004-05-02 16:56 ` Daniel Berlin
2004-05-03 7:07 ` Michael Matz
2004-03-26 22:21 Register Allocation John Lu
2004-03-26 22:21 ` Vladimir N. Makarov
2004-03-26 22:26 ` Andrew MacLeod
2004-03-27 18:22 ` Andi Kleen
2002-03-12 6:21 register Allocation Danish Samad
1997-10-14 5:51 Register allocation Thomas Koenig
1998-12-21 22:38 ` Jeffrey A Law
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=200511222256.13823.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=amacleod@redhat.com \
--cc=bergner@vnet.ibm.com \
--cc=dberlin@dberlin.org \
--cc=gcc@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).