From: Dan Cross <crossd@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: The TUHS <tuhs@tuhs.org>
Subject: Re: [TUHS] Memory management in Dennis Ritchie's C Compiler
Date: Mon, 17 Aug 2020 12:13:07 -0400 [thread overview]
Message-ID: <CAEoi9W7dNaPrUyAkCPWJGqHpyW7zqHm-Fcn2-vMBbwdKuJjZ-w@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxcyeMabfgr3WZdzM8thcnAAPtkCjoTOFwgc3a6HiZL_HQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Sat, Aug 15, 2020 at 5:52 PM Dibyendu Majumdar <mobile@majumdar.org.uk>
wrote:
> I have a project to revive the C compiler from V7/V10.
> I wanted to check if anyone here knows about the memory management in
> the compiler (c0 only for now). I am trying to migrate the memory
> management to malloc/free but I am struggling to understand exactly
> how memory is being managed.
>
I'll confess I haven't looked _that_ closely, but I rather imagine that the
V10 compiler is a descendant of PCC rather than Dennis's V6/V7 PDP-11
compiler. V10 only targets the VAX, and from what I can tell, the two
compilers in use there are LCC and PCC.
From my light skimming of V10 sources, it appears that the various
components of the default C compiler (that is, not LCC) either use
malloc/free or call `sbrk` directly.
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1205 bytes --]
next prev parent reply other threads:[~2020-08-17 16:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 21:50 Dibyendu Majumdar
2020-08-16 15:20 ` arnold
2020-08-16 15:27 ` Jim Geist
2020-08-17 16:13 ` Dan Cross [this message]
2020-08-17 20:16 ` Dibyendu Majumdar
2020-08-17 20:34 ` Paul Winalski
2020-08-17 20:43 ` Dibyendu Majumdar
2020-08-17 21:05 ` Warner Losh
2020-08-17 22:47 ` Dave Horsfall
2020-08-17 23:06 ` Nemo Nusquam
2020-08-17 21:29 ` Dibyendu Majumdar
2020-08-24 15:58 ` Dan Cross
2020-08-24 17:08 ` John Cowan
2020-08-24 17:15 ` Clem Cole
2020-08-24 17:24 ` Clem Cole
2020-08-24 17:20 ` Dan Cross
2020-08-25 23:06 ` Arthur Krewat
2020-08-17 2:02 Noel Chiappa
2020-08-17 18:02 ` Paul Winalski
2020-08-17 18:13 ` Jim Geist
2020-08-17 18:48 ` Paul Winalski
2020-08-17 19:08 ` Jim Geist
2020-08-17 19:28 ` Paul Winalski
2020-08-17 19:35 ` Jim Geist
2020-08-17 19:41 ` Richard Salz
2020-08-17 23:40 ` Steffen Nurpmeso
2020-08-17 19:27 Noel Chiappa
2020-08-17 19:30 ` Larry McVoy
2020-08-17 19:44 ` Dan Halbert
2020-08-17 19:50 ` Paul Winalski
2020-08-17 22:05 ` Arthur Krewat
2020-08-18 0:52 ` Rob Gingell
2020-08-17 19:51 Noel Chiappa
2020-08-17 22:32 Norman Wilson
2020-08-17 22:55 ` Bakul Shah
2020-08-17 23:12 ` Chet Ramey
2020-08-18 6:33 ` arnold
2020-08-25 9:36 Steve Simon
2020-08-26 13:24 Doug McIlroy
2020-08-26 15:41 ` John Cowan
2020-08-26 15:59 Noel Chiappa
2020-08-26 16:09 ` Warner Losh
2020-08-26 19:13 ` Clem Cole
2020-08-26 16:14 ` Jim Geist
2020-08-26 17:31 ` John Cowan
2020-08-27 8:37 Paul Ruizendaal
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=CAEoi9W7dNaPrUyAkCPWJGqHpyW7zqHm-Fcn2-vMBbwdKuJjZ-w@mail.gmail.com \
--to=crossd@gmail.com \
--cc=mobile@majumdar.org.uk \
--cc=tuhs@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).