From: Joe Buck <jbuck@racerx.synopsys.com>
To: mrs@windriver.com (Mike Stump)
Cc: ddolan@andrew.cmu.edu, gcc@gcc.gnu.org
Subject: Re: Tree documentation
Date: Wed, 02 Aug 2000 11:18:00 -0000 [thread overview]
Message-ID: <200008021816.LAA15500@racerx.synopsys.com> (raw)
In-Reply-To: <200008012106.OAA09277@kankakee.wrs.com>
David Dolan wrote:
> > Does any documentation of the different nodes in the GCC tree
> > structure and their fields exist? (other than the code itself) If
> > so, where can I get it.
Mike Stump wrote:
> Yes, there is a 543+ page manual.
>
> If you haven't seen it, more `find . -name *.texi -print`... Also on
> the web site, see http://gcc.gnu.org/ and look under Docs:Manual:gcc.
Mike, you've repeatedly posted messages like this to the gcc list.
These messages are frequently insulting, and in this case, simply wrong,
as the manual has no relevant information.
(it wouldn't be insulting to point someone to the manual when there is
good information there, but even in that case it could be done with less
sarcasm than is your usual style)
It makes the gcc list a more unpleasant place that you do this so much.
Since we (the SC) promised Mark Mitchell that we'd try to stamp out rude
behavior on the gcc list as one of the conditions for him taking the job,
I'm calling you on this. You need to clean up your act. It's especially
counterproductive to insult people who are trying to learn enough about
gcc internals to make significant contributions. Before hitting "send"
on gcc messages, please ask yourself whether you would feel insulted
if you were the recipient, not the sender, of one of your missives.
Before telling someone to RTFM, please make sure that there is something
relevant in the FM. In this case, had you yourself read the FM, you would
have found the following text (the last paragraph of gcc/rtl.texi):
> The proper way to interface GNU CC to a new language front end is with
> the ``tree'' data structure. There is no manual for this data
> structure, but it is described in the files @file{tree.h} and
> @file{tree.def}.
next prev parent reply other threads:[~2000-08-02 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 14:06 Mike Stump
2000-08-02 11:18 ` Joe Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 12:01 David Dolan
2000-08-01 14:12 ` Artem Khodush
2000-08-02 1:01 ` Tim Josling
2000-08-03 0:28 ` Jeffrey A Law
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=200008021816.LAA15500@racerx.synopsys.com \
--to=jbuck@racerx.synopsys.com \
--cc=ddolan@andrew.cmu.edu \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.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).