public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: John Wehle <john@feith.com>
Cc: gcc@gcc.gnu.org
Subject: Re: local-alloc update_equiv_regs and moving register initialization
Date: Thu, 14 Sep 2000 16:02:00 -0000	[thread overview]
Message-ID: <7334.968972585@upchuck> (raw)
In-Reply-To: <200009142244.SAA18278@jwlab.FEITH.COM>

  In message < 200009142244.SAA18278@jwlab.FEITH.COM >you write:
  > update_equiv_regs has the comment:
  > 
  >   /* Now scan all regs killed in an insn to see if any of them are
  >      registers only used that once.  If so, see if we can replace the
  >      reference with the equivalent from.  If we can, delete the
  >      initializing reference and this register will go away.  If we
  >      can't replace the reference, and the instruction is not in a
  >      loop, then move the register initialization just before the use,
  >      so that they are in the same basic block.  */
  > 
  > Why isn't desirable to move the register initialization just before the
  > use when both are within the same loop?
Doesn't that minimize the lifetime of the pseudo holding the initialized
value, which in turn gives the allocators more freedom in making
register assignments?

jeff

  parent reply	other threads:[~2000-09-14 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-14 15:44 John Wehle
2000-09-14 15:56 ` Joern Rennecke
2000-09-14 16:02 ` Jeffrey A Law [this message]
2000-09-14 16:09   ` Jeffrey A Law
2000-09-14 16:04 John Wehle
2000-09-14 16:22 ` Joern Rennecke
2000-09-14 16:41 John Wehle
2000-09-14 16:54 ` Joern Rennecke
2000-09-14 17:03 John Wehle

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=7334.968972585@upchuck \
    --to=law@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=john@feith.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).