From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Dave Cutler (was Re: Re: Happy birthday, Dick Hustvedt!)
Date: Wed, 21 Feb 2018 15:16:11 -0700 [thread overview]
Message-ID: <CANCZdfohedrpHj+hSZQCZ25USQqDe5n6TuGxjPpccyWY0HKbhg@mail.gmail.com> (raw)
In-Reply-To: <CAJfiPzxgnz==ZQ-c62Uv-Vec6DosRQP6x=NHsyPeHVSv54n2JQ@mail.gmail.com>
On Wed, Feb 21, 2018 at 1:18 PM, Nemo <cym224 at gmail.com> wrote:
> On 20/02/2018, George Michaelson <ggm at algebras.org> wrote (in part):
> > I don't know if we used VMS C from Dec. I have a feeling if you ran
> > Eunice, you used pcc or a derivative of pcc. Cross library calling was
> > pretty straightforward (ok, so passing function addresses and dynamic
> > structures into FORTRAN not such) [...]
>
> Hhmmm... I recall using DEC's C compiler, which we called VAX C.
> Calling C stuff from VAX FORTRAN required jiggery-pokery and the other
> way was hopeless. I recall (assuming no wetware bit-rot on my part)
> that DEC's languages did not pass on the stack but stuffed the
> arguments somewhere, passing a pointer to the somewhere.
>
The arguments were on the stack, but the calling convention also had some
metadata about the arguments you needed to worry about when calling
into/out of C, but rarely any time else. %DESCRIPTOR sticks in my head for
some traumatic reason.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180221/976ed360/attachment.html>
next prev parent reply other threads:[~2018-02-21 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 16:33 Paul Winalski
2018-02-21 1:20 ` George Michaelson
2018-02-21 20:18 ` Nemo
2018-02-21 21:33 ` Dave Horsfall
2018-02-21 22:16 ` Warner Losh [this message]
2018-02-21 22:25 ` George Michaelson
2018-02-22 2:38 ` Dave Horsfall
2018-02-22 3:25 ` [TUHS] in defense of SNOBOL, APL (and Icon) (was " Charles H. Sauer
2018-02-22 2:44 ` [TUHS] " Dave Horsfall
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=CANCZdfohedrpHj+hSZQCZ25USQqDe5n6TuGxjPpccyWY0HKbhg@mail.gmail.com \
--to=imp@bsdimp.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).