From: Daniel Berlin <dberlin@dberlin.org>
To: Jeffrey A Law <law@redhat.com>
Cc: Steven Bosscher <stevenb@suse.de>,
gcc@gcc.gnu.org, Daniel Towner <daniel.towner@picochip.com>,
Vladimir Makarov <vmakarov@redhat.com>,
Nathan Sidwell <nathan@codesourcery.com>,
rth@redhat.com
Subject: Re: Incorrect DFA scheduling of output dependency.
Date: Tue, 07 Dec 2004 13:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.60.0412070838100.806@dberlin.org> (raw)
In-Reply-To: <1102425913.18302.329.camel@localhost.localdomain>
>> FSFChangeLog.11: * combine.c (try_combine): Clear reg_n_refs if i2dest is not
>> haifa-sched.c: be correct. Namely: reg_n_refs, reg_n_sets, reg_n_deaths,
>> sched-deps.c: Otherwise, the reg_n_refs info (which depends on loop_depth) would
>>
>> So even in the ChangeLogs there is only one reference to reg_n_regs.
>>
>> Is this bitrot?
> reg_n_refs got moved into the reg_info_def structure along with most of
> the other information related to registers. The comment needs updating.
> jeff
Just to followup, it's now REG_N_REFS, defined in regs.h
--Dan
next prev parent reply other threads:[~2004-12-07 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 11:30 Daniel Towner
2004-12-06 12:30 ` Nathan Sidwell
2004-12-06 12:31 ` Steven Bosscher
2004-12-06 16:27 ` Daniel Towner
2004-12-06 17:12 ` Vladimir Makarov
2004-12-07 10:59 ` Daniel Towner
2004-12-07 13:01 ` Steven Bosscher
2004-12-07 13:15 ` Steven Bosscher
2004-12-07 13:26 ` Jeffrey A Law
2004-12-07 13:40 ` Daniel Berlin [this message]
2004-12-07 22:15 ` Vladimir N. Makarov
[not found] ` <41B6360E.6010806@redhat.com>
2004-12-08 9:53 ` Daniel Towner
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=Pine.LNX.4.60.0412070838100.806@dberlin.org \
--to=dberlin@dberlin.org \
--cc=daniel.towner@picochip.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=nathan@codesourcery.com \
--cc=rth@redhat.com \
--cc=stevenb@suse.de \
--cc=vmakarov@redhat.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).