From: Brantley Coile <brantleycoile@me.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Compiling ken-cc on Linux
Date: Thu, 26 Nov 2015 19:02:13 -0500 [thread overview]
Message-ID: <549869E7-C18F-43D2-A90A-12D7FF1120EE@me.com> (raw)
In-Reply-To: <CAOw7k5heCVvBLOpMotWw9fnrVmHz-9M3n4PfoBZhsSdTR_OVHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Clearly history is wrong. It would never be able to compile C in less than 18MB (1/2 of clang’s text size). Therefor Unix didn’t really happen. It’s all been a phone company conspiracy for world domination, like the NASA not really putting a man on the moon. We were just *told* they had built a system in 1973 using a simple two pass compiler that would fit into about 28KW of memory. AT&T would have gotten away with it too, if it weren’t for their great mistake—the 3B20. Results: no more “One system; it works."
> On Nov 26, 2015, at 6:21 PM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
>
> On 26 November 2015 at 23:08, Ryan Gonzalez <rymg19@gmail.com <mailto:rymg19@gmail.com>> wrote:
> Holy crap, that's crazy. I built it in debug mode on Linux, but I don't think it used that much. I only have 6 GB right now!
>
> You have to remember that a C compiler is one of the largest, most complex software components that human beings have ever had to produce.
> The original C reference manual made it look deceptively easy, but really there's a ton of stuff going on in there, as you can see.
> How they ever got it going on a system with 64Kbytes of address space, I'll never know.
[-- Attachment #2: Type: text/html, Size: 2055 bytes --]
next prev parent reply other threads:[~2015-11-27 0:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:10 Vasudev Kamath
2015-11-25 17:15 ` Ryan Gonzalez
2015-11-25 17:24 ` Vasudev Kamath
2015-11-26 12:08 ` Charles Forsyth
2015-11-27 16:50 ` Vasudev Kamath
2015-11-27 16:59 ` Ryan Gonzalez
2015-11-27 17:16 ` Vasudev Kamath
2015-11-27 18:24 ` Ryan Gonzalez
2015-11-29 9:41 ` Vasudev Kamath
2015-11-29 14:38 ` Ryan Gonzalez
2015-11-27 18:11 ` trebol
2015-11-26 12:10 ` Charles Forsyth
2015-11-26 12:18 ` David du Colombier
2015-11-26 18:15 ` Ryan Gonzalez
2015-11-26 21:31 ` Charles Forsyth
2015-11-26 21:49 ` Ryan Gonzalez
2015-11-26 21:51 ` Charles Forsyth
2015-11-26 21:56 ` Charles Forsyth
2015-11-26 22:02 ` Ryan Gonzalez
2015-11-26 22:08 ` Charles Forsyth
2015-11-26 22:30 ` David du Colombier
2015-11-26 23:08 ` Ryan Gonzalez
2015-11-26 23:21 ` Charles Forsyth
2015-11-26 23:41 ` Ryan Gonzalez
2015-11-27 0:02 ` Brantley Coile [this message]
2015-11-27 8:13 ` Giacomo Tesio
2015-11-27 8:56 ` arnold
2015-11-27 13:33 ` Steffen Nurpmeso
2015-11-28 0:55 ` erik quanstrom
2015-11-30 15:46 ` Steffen Nurpmeso
2015-11-27 12:42 ` tlaronde
2015-11-27 14:07 ` Giacomo Tesio
2015-11-27 14:34 ` tlaronde
2015-11-28 1:01 ` erik quanstrom
2015-11-27 12:05 ` Steffen Nurpmeso
2015-11-27 12:32 ` lucio
2015-11-26 21:40 ` Andrew Simmons
2015-11-28 6:42 da Tyga
2015-11-28 7:40 ` Brantley Coile
2015-11-28 20:31 ` Anthony Sorace
2015-11-28 23:33 ` Brantley Coile
2015-11-29 6:12 ` lucio
2015-11-28 20:13 ` Ryan Gonzalez
2015-11-29 5:57 ` lucio
2015-11-29 16:17 ` tlaronde
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=549869E7-C18F-43D2-A90A-12D7FF1120EE@me.com \
--to=brantleycoile@me.com \
--cc=9fans@9fans.net \
/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).