From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Zack Weinberg <zackw@panix.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: target hooks for the scheduler
Date: Thu, 16 Aug 2001 10:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0108161828400.3062-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20010816020315.A15039@panix.com>
Zack Weinberg wrote:
> * target.h: Forward declare union tree_node. Change all uses
> of "tree" to "union tree_node *". Add hooks for scheduler:
I thought we'd decided that the way to go on this was to arrange for some
suitable header to forward declare union tree_node and struct rtx_def then
typedef tree and rtx, so those names are visible everywhere, then
gradually change existing uses of union tree_node * to just use tree,
etc.?
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-08-16 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 23:03 Zack Weinberg
2001-08-16 3:42 ` Hans-Peter Nilsson
2001-08-16 10:24 ` Neil Booth
2001-08-16 11:08 ` Zack Weinberg
2001-08-16 10:31 ` Joseph S. Myers [this message]
2001-08-16 11:07 ` Zack Weinberg
2001-08-16 16:51 ` Richard Henderson
2001-08-16 18:12 ` Zack Weinberg
2001-08-16 18:18 ` Richard Henderson
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.33.0108161828400.3062-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=zackw@panix.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).