The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: vasco@icpnet.pl (Andrzej Popielewicz)
Subject: [TUHS] gcc-3.4.6 and old unix
Date: Mon, 24 Apr 2006 09:33:34 +0200	[thread overview]
Message-ID: <444C7F4E.7040906@icpnet.pl> (raw)
In-Reply-To: <444C1CDD.20805@pacbell.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

Michael Davidson napisał(a):

>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 ]
>
>
>_______________________________________________
>TUHS mailing list
>TUHS at minnie.tuhs.org
>https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>  
>
What about creating "old unix" version of djgpp. djgpp compiler is 32 
bit "gcc" running in 16 bit DOS.
Perhaps DeJorie could help.

Andrzej



  reply	other threads:[~2006-04-24  7: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
2006-04-24  7:33   ` Andrzej Popielewicz [this message]
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=444C7F4E.7040906@icpnet.pl \
    --to=vasco@icpnet.pl \
    /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).