From: patv@monmouth.com (patv@monmouth.com)
Subject: [TUHS] [pups] gcc-3.4.6 and old unix
Date: Tue, 25 Apr 2006 07:53:28 EST [thread overview]
Message-ID: <200604251253.k3PCrR0f005871@wwws.monmouth.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
If this helps at all, I've been working (very, very slowly) on a port of
v32 to Intel platforms. At first I used gcc for some kernel work, but
quickly realized that it would be overwhelming to the final v7 system.
Since I don't want to do the work twice, I looked for a different compiler
suite. I switched to the ACK compiler suite and just finished the WinXP
cross compiler work. It has a pdp11 back end, which I have yet to try,
that may be useful.
It isn't gcc, but ir does do ANSI C and the i386 assembler seems to be
pretty complete. Let me know if there's any interest and I'll put it up
on my site for download.
Pat
> Toby Thain napisał(a):
>
> >On 24-Apr-06, at 9:05 AM, Wesley Parish wrote:
> >
> >
> >
> >>Quoting Andrzej Popielewicz <vasco at icpnet.pl>:
> >>
> >>
> >>
> >>>Wesley Parish napisał(a):
> >>>
> >>>
> >>>
> >
> >It can't be done.
> >
> >As others point out, the program is many times (100x or more?) too
> >big -- likely even gcc 1.x is far too big, but gcc {2,3,4}.x are all
> >meant for large 32-bit systems.
> >
> >However, cross-compilation can certainly be easily done. I have made
> >a PDP-11 back-end for lcc[1] (not quite complete but shows that it
> >can be done), which is an ANSI (c89) compiler[2]. lcc is a much
> >smaller and simpler compiler than gcc, but its executables are still
> >massively outsize for PDP-11 systems.
> >
> >
> Yes, even running vi or csh in Ultrix (in simh pdp11) produced message :
> too big. After setting cpu to 3072K it worked(setting to 4096 K hanged
> the system BTW).
> Cross compilation has also this advantage , that You have better editors
> to Your disposal and You can work faster.
> Well native cc seems to be good enough, using pdp11 in emulator we have
> anyway only hobbyst license .
>
> Andrzej
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
---------------------------------------------
This message was sent using Monmouth Internet MI-Webmail.
http://www.monmouth.com/
next reply other threads:[~2006-04-25 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 12:53 patv [this message]
2006-05-02 16:52 ` Charlie ROOT
2006-05-03 1:17 ` Pat Villani
-- strict thread matches above, loose matches on Subject: below --
2006-04-23 23:27 [TUHS] " Bill Cunningham
2006-04-24 0:33 ` Michael Davidson
2006-04-24 7:33 ` Andrzej Popielewicz
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
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=200604251253.k3PCrR0f005871@wwws.monmouth.com \
--to=patv@monmouth.com \
/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).