Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: gah4 <gah4@u.washington.edu>
Newsgroups: comp.compilers
Subject: Re: PALM challenge
Date: Sat, 1 Oct 2022 17:09:53 -0700 (PDT)
Organization: Compilers Central
Lines: 16
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <22-10-005@comp.compilers>
References: <22-10-001@comp.compilers>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="14918"; mail-complaints-to="abuse@iecc.com"
Keywords: architecture, history
Posted-Date: 01 Oct 2022 21:35:17 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
In-Reply-To: <22-10-001@comp.compilers>
Xref: csiph.com comp.compilers:3182

On Saturday, October 1, 2022 at 12:16:25 PM UTC-7, lewi...@gmail.com wrote:
> Lots of new CPUs, sure.

> But let's explore an old CPU: the 1975 PALM.

> I'm looking for anyone interested to explore the idea. Maybe prove how
> robust modern tools are at adapting C, by exploring this ancient instruction
> set.

My favorite for adapting C to new (or old) hardware is LCC.

You only have to rewrite the code generator, and it has a code generator
generator to make it easier.  The usual case, as with many Unix C
compilers, is to write out assembly code, and feed it to an assembler.

Since you already have an assembler, it should be pretty fast.