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=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5392 invoked from network); 16 Aug 2020 15:28:27 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 16 Aug 2020 15:28:27 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 5D7879DF6C; Mon, 17 Aug 2020 01:28:26 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5D82A9B5EC; Mon, 17 Aug 2020 01:28:10 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="rUqVkQjm"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id B210F9B5EC; Mon, 17 Aug 2020 01:28:06 +1000 (AEST) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by minnie.tuhs.org (Postfix) with ESMTPS id 559A89B5D7 for ; Mon, 17 Aug 2020 01:28:05 +1000 (AEST) Received: by mail-wr1-f51.google.com with SMTP id l2so12483339wrc.7 for ; Sun, 16 Aug 2020 08:28:05 -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=mHg6S+wT5NX/5uksRrsha8mDNxcpDqPRMNBG2ZEWBZM=; b=rUqVkQjmzaDh/MBUBxOR7D2v6Y3EeFzB2hZNTjKlzM/4eMimoNwRksIuQMA5KB5eo1 P+VmyT7v/2h+mJ0yZSWHOTROETCdHn8IZpIuxfKeyXsAvnABnjEEhDMkCNn//YZDJyl+ 0DYz8K1yWB0N4H6k4eITjvEevoy8VbYjSq1hZ7D7NHUd3/DGBtnZhqb0eRN/hRSnkK8f AqY4YQH8BKr1t6BZG/QiiMv3+sGYzDqsH0cgQ9xmLUfgK+a/VRRViQxNl7NJ+ExaA9Zq DJBZAbArLPJPML1bUw/x2nUnLgW1okww7IkygZm9tJKQZKl5/k7Nc1ahEnoOOon4OMjC PTsw== 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=mHg6S+wT5NX/5uksRrsha8mDNxcpDqPRMNBG2ZEWBZM=; b=sa8Z6nt20PJMsugBugRMmFY+qlU0INwVJil2rElDv7mNZEXw2/yjcO48R76Cnp7dYn m9qVYPgkHmkPJah1/WuHxX5jY3LiBNSS8cWTeYTkg/hv9IoAAydGD7bDvdDw+Wlbv3mF FfjOsmmX0gN2PmeqmF0nWeLxnAHWyS4C6iHmXuU5YmR7cvlSeZcPQOyTdoXDjpKdz2AZ Cfm//eS6dNRj22xHVEb7ay8Kky3LyOUMSE9i5dDUE8YqswJawEzDsd7nbo3SXWCkxA1H /LYxyXPcV1bJnlUARY/rVhIWdlgXwejHhXoYhVe5xxm5R/jHwWUDrxOR+fqU2bh6/LOo FgeQ== X-Gm-Message-State: AOAM533jwI1p78wpfJPoRwMI5U6rTs/sNSj/8khroaiOueuwrZDRW4EN EFFwFXrSE035tlwlod0sQcoqvcDxuRWj46I1Qm0= X-Google-Smtp-Source: ABdhPJyVcj9DHw3h73m2WEzVLm5qHaRv00aO1fH7PblZmq+/ddI0ePMON2av32XYywS55xSxa0mZ4drvbSvmvgD8Wvk= X-Received: by 2002:adf:ec4f:: with SMTP id w15mr10632148wrn.385.1597591684011; Sun, 16 Aug 2020 08:28:04 -0700 (PDT) MIME-Version: 1.0 References: <202008161520.07GFKg9k028970@freefriends.org> In-Reply-To: <202008161520.07GFKg9k028970@freefriends.org> From: Jim Geist Date: Sun, 16 Aug 2020 11:27:52 -0400 Message-ID: To: arnold@skeeve.com Content-Type: multipart/alternative; boundary="000000000000d25b0005ad004c3d" 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 Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000d25b0005ad004c3d Content-Type: text/plain; charset="UTF-8" Do you have a link to the V10 compiler source? On Sun, Aug 16, 2020 at 11:21 AM wrote: > Dibyendu Majumdar wrote: > > > Hi, > > > > 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. > > > > Thanks and Regards > > Dibyendu > > There already is a project that revived PCC, probably starting > with the one in 4BSD. > > http://pcc.ludd.ltu.se/ > > I have a git mirror, just to make things easier for access through > firewalls: > > https://github.com/arnoldrobbins/pcc-revived > > Starting from the V10 compiler would be interesting. It was not available > when the above project was started. > > HTH, > > Arnold > --000000000000d25b0005ad004c3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Do you have a link to the V10 compiler source?

On Sun, Aug = 16, 2020 at 11:21 AM <arnold@skeeve= .com> wrote:
Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:

> Hi,
>
> 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<= br> > 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.
>
> Thanks and Regards
> Dibyendu

There already is a project that revived PCC, probably starting
with the one in 4BSD.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://pcc.ludd.ltu.se/

I have a git mirror, just to make things easier for access through
firewalls:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://github.com/arnoldrob= bins/pcc-revived

Starting from the V10 compiler would be interesting. It was not available when the above project was started.

HTH,

Arnold
--000000000000d25b0005ad004c3d--