From: peterjeremy@optushome.com.au (Peter Jeremy)
Subject: [TUHS] gcc-3.4.6 and old unix
Date: Mon, 24 Apr 2006 10:00:46 +1000 [thread overview]
Message-ID: <20060424000046.GE720@turion.vk2pj.dyndns.org> (raw)
In-Reply-To: <000701c6672d$8d6f2ae0$2f01a8c0@myhome.westell.com>
On Sun, 2006-Apr-23 19:27:55 -0400, Bill Cunningham wrote:
> Has anyone thought of or tried to port the gcc to the old unixes?
What do you mean by "old unixes"? 32V or 4BSD would be trivial. 2BSD
or V7 (or earlier) would be virtually impossible. gcc was born in a
32-bit world and there's no way you will get it to work natively on a
16-bit host (though it does have a PDP-11 backend): Both the code and
data structures assume a large memory space and are not amenable to
using overlays.
If you really wanted to run gcc on a PDP-11, the easiest (though very
slow) solution would be to build a simple 32-bit virtual machine that
runs on the PDP-11 and run gcc within it.
> A C compiler that would work with modern c89 or c99.
As far as I can tell, C99 was deliberately designed to make it
impossible to build a simple C compiler.
--
Peter Jeremy
next prev parent reply other threads:[~2006-04-24 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 23:27 Bill Cunningham
2006-04-24 0:00 ` Peter Jeremy [this message]
2006-04-24 0:33 ` Michael Davidson
2006-04-24 7:33 ` Andrzej Popielewicz
2006-04-24 7:47 ` Peter Jeremy
2006-04-24 8:44 ` Wesley Parish
2006-04-24 9:50 ` Andrzej Popielewicz
2006-04-24 13:05 ` [TUHS] [pups] " Wesley Parish
2006-04-24 16:06 ` Toby Thain
2006-04-25 6:28 ` Andrzej Popielewicz
2006-04-24 9:29 ` [TUHS] " Lars Brinkhoff
2006-04-24 12:53 ` John Cowan
2006-04-24 18:01 Jose R Valverde
2006-05-02 17:09 ` A. Wik
2006-05-02 17:57 ` M. Warner Losh
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=20060424000046.GE720@turion.vk2pj.dyndns.org \
--to=peterjeremy@optushome.com.au \
/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).