From: michael_davidson@pacbell.net (Michael Davidson)
Subject: [TUHS] gcc-3.4.6 and old unix
Date: Sun, 23 Apr 2006 17:33:33 -0700 [thread overview]
Message-ID: <444C1CDD.20805@pacbell.net> (raw)
In-Reply-To: <000701c6672d$8d6f2ae0$2f01a8c0@myhome.westell.com>
Bill Cunningham wrote:
> Has anyone thought of or tried to port the gcc to the old unixes? It
>would have to be a very scaled down version. A C compiler that would work
>with modern c89 or c99. Something to get a C compiler working that would
>compile todays programs. The old C compilers can be kept for safekeeping as
>they don't work much anymore.
>
>
By "the old unixes" I assume that you mean things like V6 and V7
for the PDP-11.
Both gcc and GNU binutils already support PDP-11 targets, at
least to some extent, so you can already do cross development
targeted at the PDP-11.
Trying to actually host gcc on a 16 bit UNIX system is almost
certainly a completely futile and pointless exercise - it is many,
*many* times too big and I am pretty sure that it assumes at
least a 32 bit host - if you cut it down enough so that it fit it
isimply wouldn't be gcc any more.
I suspect that you would also find that most of "todays programs"
wouldn't fit either ...
Michael Davidson
[ and, actually, the old C compiuers still work just fine for
ompiling the code that they were priginally intended for ]
next prev parent reply other threads:[~2006-04-24 0:33 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
2006-04-24 0:33 ` Michael Davidson [this message]
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=444C1CDD.20805@pacbell.net \
--to=michael_davidson@pacbell.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).