From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32320 invoked from network); 17 Aug 2020 16:14:29 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 17 Aug 2020 16:14:29 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id B41D59E190; Tue, 18 Aug 2020 02:14:23 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 723119CAB1; Tue, 18 Aug 2020 02:13:48 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="CnHrBeuL"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id D4CF09CAAF; Tue, 18 Aug 2020 02:13:45 +1000 (AEST) Received: from mail-qv1-f42.google.com (mail-qv1-f42.google.com [209.85.219.42]) by minnie.tuhs.org (Postfix) with ESMTPS id 032609C8BB for ; Tue, 18 Aug 2020 02:13:45 +1000 (AEST) Received: by mail-qv1-f42.google.com with SMTP id l13so8015259qvt.10 for ; Mon, 17 Aug 2020 09:13:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Pqfl2GN7+ItzmMGSEbkfidWiWMAwqaLsgpM8MLUytCU=; b=CnHrBeuLMMtgRAOwK4FtAj1lvi8qn0z03GdEfwdWOOnz1jWc7d+JjWZt2zcXC4qHhm 0V0y5w3pkhTWw/SncCxbnUXFHY6rk/ZK0CeQeyY7Tl38MXKr1UA70Dvlx3gklWO2AW0D c+TmOE9ChUVm9/1ViJmhGnBmJ5TMGrxNzOVLGkLehlEWS69qPdETMJrs5zqQToGQEvAn sR4p6g/NRo2Wk1/wsaWwFTPFzu4dS39NX82/sFZGiI6q+jtqrtuwl2MZ8mh/dKfkio9O 0IK0VvPzZ4grYiFkMNXCA0xBM1LINK80L7qgiFN7fr0syzzenOmje6NLzSQcsp2q7RXX 84ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Pqfl2GN7+ItzmMGSEbkfidWiWMAwqaLsgpM8MLUytCU=; b=WFXqDmA2wgkfKJl0JwpNeKq4Uav/olnE4rLhBhBrSUq3K/iarxfXQUihL9TOGX8mGF ys80jpu4bkWnhvMzeGrMMock/4D2gy2McsTp0DVAUg0zBTVpeO79LAqP1buq/xWcdLU8 RG+QhgTpjnExNCbV05vGNDizQBofNcPR3o96hwKcHJigkQrj6+4AJ1QCc6cxwcANuhyu fhuiy3hOca2Px61GB7RJNxKCsaBYiCflE/VVNu78KXlDw7POZCG7tVYxAM1tIaL/S/cF tH5KLVa9gT4DqOgFy+OpCkp0U8UbDVrDiizKMfdOJOadbQTbZaSjKVDcugA/QO5zyfKh twrA== X-Gm-Message-State: AOAM531E1raB3vECfhP2x7mlB7HT756bL5ySjqOz6+qrJ35mYx3x7Aj5 Kb5WEkh8XVYiCXytznyiU6BP4Dth3YP1s2N6WGLcEowWWMI= X-Google-Smtp-Source: ABdhPJz90XvRlkA0HKCQT/l1PyWH0SheVKwYFuqB/D0Z2LmpAgcbmenGExoqaoVrnEOAFMy1a/BYgW4OXLOoLqCh5uo= X-Received: by 2002:a0c:f1c9:: with SMTP id u9mr15008620qvl.76.1597680823985; Mon, 17 Aug 2020 09:13:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dan Cross Date: Mon, 17 Aug 2020 12:13:07 -0400 Message-ID: To: Dibyendu Majumdar Content-Type: multipart/alternative; boundary="000000000000fa73b305ad150d02" Subject: Re: [TUHS] Memory management in Dennis Ritchie's C Compiler X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The TUHS Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000fa73b305ad150d02 Content-Type: text/plain; charset="UTF-8" On Sat, Aug 15, 2020 at 5:52 PM Dibyendu Majumdar 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. --000000000000fa73b305ad150d02 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 c= onfess I haven't looked _that_ closely, but I rather imagine that the V= 10 compiler is a descendant of PCC rather than Dennis's V6/V7 PDP-11 co= mpiler. V10 only targets the VAX, and from what I can tell, the two compile= rs in use there are LCC and PCC.

From my light ski= mming 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` direct= ly.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dan C.

--000000000000fa73b305ad150d02--