From: "Vladimir N. Makarov" <vmakarov@redhat.com>
To: John Lu <jlu@lsil.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Register Allocation
Date: Fri, 26 Mar 2004 22:21:00 -0000 [thread overview]
Message-ID: <40648F84.5070704@redhat.com> (raw)
In-Reply-To: <200403261954.i2QJsfT27909@dts0.lsil.com>
John Lu wrote:
>Hi,
>
>I've been working on a port based on gcc-3.3 and I've noticed that
>better assembly code is generated if the C source has
>separate variables declared for distinct live ranges.
>
>
>
Pesudo-register renaming is made by -fweb. It was written by Jan
Hubicka. Probably, this option should be set up by default (although
there is no practically improvement for SPECInt2000 for P4, some tests
are really faster). Another positive thing of usage this option is
better scheduling because of less anti-dependences.
Different live ranges of a varaible sometimes has less conflicts and
never more. Therefore there is more probablility that varaible values
will be in registers. New ra works on webs (it is definitions and
usages of pseudo-register which can have different names). So it should
work for new ra too. But there are a lot factors which could prevent
generates a better code.
Vlad
>
>
next prev parent reply other threads:[~2004-03-26 20:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 22:21 John Lu
2004-03-26 22:21 ` Vladimir N. Makarov [this message]
2004-03-26 22:26 ` Andrew MacLeod
2004-03-27 18:22 ` Andi Kleen
-- 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
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
[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
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
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=40648F84.5070704@redhat.com \
--to=vmakarov@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jlu@lsil.com \
/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).