From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] compilers
Date: Sat, 26 Mar 2005 15:43:45 -0500 [thread overview]
Message-ID: <ee9e417a05032612434547d5ca@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.61.0503261011280.25349@malasada.lava.net>
> The compilers share a bit of code through copy-paste. I was wondering
> if there are any important changes in recent years that were made
> in a popularly used compiler (ie. 8[cal]) that might benefit other
> compilers (ie. k[cal])?
We do try to make the changes in all the compilers when
the changes are general, though that's no guarantee that
things haven't slipped through.
> Also, is there any documentation out there other than "How to
> Use the Plan 9 C Compiler" and "Plan 9 C Compilers" that cover
> the compilers? I've been perusing the code and some of the
> code takes quite a while to figure out. Some quick notes would
> go a long way (ie. "this function is a recursive tree walk that
> checks types and inserts casts").
A more detailed implementation document for any one
of the compilers is yet to be written.
More seriously, I found that matching the text in
section 5 of /sys/doc/compiler.ps against the compiler
code was quite informative. It would be great if
there were better documentation.
Russ
next prev parent reply other threads:[~2005-03-26 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 20:16 Tim Newsham
2005-03-26 20:43 ` Russ Cox [this message]
2005-03-27 6:01 ` kazumi iwane
2005-03-27 6:04 ` boyd, rounin
2005-03-27 14:56 ` Russ Cox
2005-03-28 23:50 ` boyd, rounin
2005-03-27 16:40 ` Charles Forsyth
2005-03-28 15:27 ` [9fans] ts7200 Ronald G. Minnich
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=ee9e417a05032612434547d5ca@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).