From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Early Unix function calls: expensive?
Date: Tue, 5 Jan 2016 12:46:05 -0500 [thread overview]
Message-ID: <2C046974-5E68-416F-9413-2FAD3D3D67EC@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2NdctE4cmNQxmjdVG7_eWkyyQ24X3AFBUDDVOoanteO9A@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
No, to my knowledge NO compiler I ever came across (I worked on the dark side DOS BATCH, RT-11, RSX-11, and RSTS-11 in various languages though primarily MACRO-11 and FORTRAN) ever used this linkage. Certainly, none of the UNIX products did. It was goofy. We played around with it and it just didn’t do anything you couldn’t do better with JSR/RET and some clever stack manipulation with MOV instructions.
> On Jan 5, 2016, at 12:43 PM, Clem Cole <clemc at ccc.com> wrote:
>
>
> On Tue, Jan 5, 2016 at 12:28 PM, Ronald Natalie <ron at ronnatalie.com <mailto:ron at ronnatalie.com>> wrote:
> I remember going to the T11 (PDP-11 on a single chip) announcement and having them say the complete instruction set was supported with the exception of MARK.
>
> right... which is why I don't think FTN use it, or the HW folks would have been forced to put it in.
>
> Clem
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160105/b84651c3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2284 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160105/b84651c3/attachment.bin>
next prev parent reply other threads:[~2016-01-05 17:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 23:35 Warren Toomey
2016-01-03 23:53 ` Tim Bradshaw
2016-01-04 0:01 ` John Cowan
2016-01-04 4:40 ` Armando Stettner
2016-01-04 8:52 ` Tim Bradshaw
2016-01-04 17:29 ` Larry McVoy
2016-01-04 13:50 ` Clem Cole
2016-01-05 2:00 ` Ronald Natalie
2016-01-05 15:13 ` Clem Cole
2016-01-05 16:46 ` John Cowan
2016-01-05 17:33 ` Diomidis Spinellis
2016-01-05 17:42 ` Clem Cole
2016-01-05 17:28 ` Ronald Natalie
2016-01-05 17:43 ` Clem Cole
2016-01-05 17:46 ` Ronald Natalie [this message]
2016-01-05 18:03 ` Warner Losh
2016-01-05 18:24 ` Ronald Natalie
2016-01-05 20:26 ` scj
2016-01-05 20:49 ` John Cowan
2016-01-05 23:24 ` Dave Horsfall
2016-01-05 23:55 ` Ronald Natalie
2016-01-04 0:00 ` John Cowan
2016-01-04 0:42 ` scj
2016-01-04 11:35 ` Tony Finch
[not found] <mailman.3.1451865187.15972.tuhs@minnie.tuhs.org>
2016-01-04 1:08 ` Johnny Billquist
2016-01-04 1:29 ` Larry McVoy
2016-01-04 1:31 Noel Chiappa
2016-01-04 2:24 ` scj
2016-01-04 4:24 ` Larry McVoy
2016-01-04 1:59 Norman Wilson
2016-01-04 15:09 ` John Cowan
2016-01-04 2:21 Clem Cole
2016-01-04 12:53 Noel Chiappa
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=2C046974-5E68-416F-9413-2FAD3D3D67EC@ronnatalie.com \
--to=ron@ronnatalie.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).