From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: gcc@gcc.gnu.org
Cc: wilson@cygnus.com
Subject: update_life_info in schedule_insns
Date: Fri, 27 Dec 2002 12:49:00 -0000 [thread overview]
Message-ID: <20021227192545.GA9542@atrey.karlin.mff.cuni.cz> (raw)
Hello,
> /* Don't update reg info after reload, since that affects
> regs_ever_live, which should not change after reload. */
> update_life_info (blocks, UPDATE_LIFE_LOCAL,
> (reload_completed ? PROP_DEATH_NOTES
> : PROP_DEATH_NOTES | PROP_REG_INFO));
> if (any_large_regions)
> {
> update_life_info (large_region_blocks, UPDATE_LIFE_GLOBAL,
> PROP_DEATH_NOTES | PROP_REG_INFO);
> }
why the comment above does not apply for the second update_life_info
call?
Zdenek
next reply other threads:[~2002-12-27 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 12:49 Zdenek Dvorak [this message]
2002-12-27 14:14 ` Jan Hubicka
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=20021227192545.GA9542@atrey.karlin.mff.cuni.cz \
--to=rakdver@atrey.karlin.mff.cuni.cz \
--cc=gcc@gcc.gnu.org \
--cc=wilson@cygnus.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).