Re: PALM challenge

gah4 <gah4@u.washington.edu>
Sat, 1 Oct 2022 17:09:53 -0700 (PDT)

          From comp.compilers
Related articles
PALM challenge lewissa78@gmail.com (Steve Lewis) (2022-10-01)
Re: PALM challenge gah4@u.washington.edu (gah4) (2022-10-01)
Re: PALM challenge tkoenig@netcologne.de (Thomas Koenig) (2022-10-02)
Re: PALM challenge gah4@u.washington.edu (gah4) (2022-10-03)
| List of all articles for this month |
From: gah4 <gah4@u.washington.edu>
Newsgroups: comp.compilers
Date: Sat, 1 Oct 2022 17:09:53 -0700 (PDT)
Organization: Compilers Central
References: 22-10-001
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
In-Reply-To: 22-10-001

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.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.