From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] reviving a bit of WWB
Date: Tue, 22 Sep 2020 11:33:22 -0400 [thread overview]
Message-ID: <CAC20D2PL+JVkaidN-2omAKRpmLHBUFm9P-8ogSTLoQKEHXLZWQ@mail.gmail.com> (raw)
In-Reply-To: <CAD2gp_SVNZujYb+h=q6_bY6BiFa_BvxcGqPMQpsFFBzYEzMRQA@mail.gmail.com>
Moving to COFF
On Mon, Sep 21, 2020 at 7:56 PM John Cowan <cowan at ccil.org> wrote:
> Rereading that made me wonder: if someone retargeted an old compiler (pcc,
> say) to produce i386 code,
>
I thought SVR3's was PCC (maybe PCC2). But I thought I remember that is
had a i386 code. Certainly by SVR4 time.
IIRC, the time frame of SVR3's front end would have been original ANSI
(i.e. White Book V2).
> how much faster would it run than a VAX?
>
In the time frame of the SVR3 (mid/late 80s), the Intel processors was
faster than the 1MIP (780 circa 1977) in raw computes. The issue was
always I/O. Most PC did not have the same amount of I/O HW that much
earlier Vaxen.
> I see that there is a pcc derivative at <http://pcc.ludd.ltu.se/>, but
> supposedly it has been heavily rewritten for C99 compliance and other
> things.
>
And my point is that by the time of C99, it was a different language than
the early 1970s when Dennis created fit or the original PDP-11/20 he and
Ken used for the first UNIX kernel and tools implementations.
"When I read commentary about suggestions for where C should go, I often
think back and give thanks that it wasn't developed under the advice of a
worldwide crowd." dmr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200922/f07bce85/attachment.htm>
parent reply other threads:[~2020-09-22 15:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAD2gp_SVNZujYb+h=q6_bY6BiFa_BvxcGqPMQpsFFBzYEzMRQA@mail.gmail.com>]
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=CAC20D2PL+JVkaidN-2omAKRpmLHBUFm9P-8ogSTLoQKEHXLZWQ@mail.gmail.com \
--to=coff@minnie.tuhs.org \
/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).