From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] allocate combine.c:LOG_LINKS in an obstack
Date: Tue, 05 Apr 2011 15:07:00 -0000 [thread overview]
Message-ID: <BANLkTimdfDQQVWRpW=hJ8dhR1+Ja8nR=6g@mail.gmail.com> (raw)
In-Reply-To: <20110405145107.GH23480@codesourcery.com>
On Tue, Apr 5, 2011 at 4:51 PM, Nathan Froyd <froydnj@codesourcery.com> wrote:
> On Tue, Apr 05, 2011 at 04:42:27PM +0200, Steven Bosscher wrote:
>> On Tue, Apr 5, 2011 at 3:59 PM, Nathan Froyd <froydnj@codesourcery.com> wrote:
>> > v2, now with obstacks!
>>
>> @findex LOG_LINKS
>> @item LOG_LINKS (@var{i})
>> A list (chain of @code{insn_list} expressions) giving information about
>> dependencies between instructions within a basic block. Neither a jump
>> nor a label may come between the related insns. These are only used by
>> the schedulers and by combine. This is a deprecated data structure.
>> Def-use and use-def chains are now preferred.
>
> So, being somewhat RTL-ignorant, is this patch going in the wrong
> direction?
Oh, not at all. Just documentation that needs updating! :)
Ciao!
Steven
next prev parent reply other threads:[~2011-04-05 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 18:50 [PATCH] allocate combine.c:LOG_LINKS in an alloc_pool Nathan Froyd
2011-04-04 19:01 ` Steven Bosscher
2011-04-04 19:25 ` Nathan Froyd
2011-04-05 10:14 ` Richard Guenther
2011-04-05 14:00 ` [PATCH] allocate combine.c:LOG_LINKS in an obstack Nathan Froyd
2011-04-05 14:12 ` Richard Guenther
2011-04-05 14:43 ` Steven Bosscher
2011-04-05 14:51 ` Nathan Froyd
2011-04-05 15:07 ` Steven Bosscher [this message]
2011-04-05 16:13 ` Jeff Law
2011-04-05 18:23 ` Nathan Froyd
2011-04-05 18:28 ` Nathan Froyd
2011-04-05 19:29 ` H.J. Lu
2011-04-05 19:34 ` Nathan Froyd
2011-04-05 19:32 ` H.J. Lu
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='BANLkTimdfDQQVWRpW=hJ8dhR1+Ja8nR=6g@mail.gmail.com' \
--to=stevenb.gcc@gmail.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@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).