Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #135658

Re: First result in riscv optimiser

Path csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From Kragen Javier Sitaker <kragen@canonical.org>
Newsgroups comp.lang.forth
Subject Re: First result in riscv optimiser
Date Fri, 11 Sep 2026 07:50:13 -0300
Organization Primarily biological and memetic
Lines 28
Message-ID <877bksdpui.fsf@debian> (permalink)
References <nnd$172defd2$1b2df6f6@e430673098f06a19> <87ecf96ljg.fsf@debian> <nnd$23c5006f$6f768ed1@9c6c99f017e8c6d5> <87y0dcgvxf.fsf@debian> <nnd$2a0f5231$3093e519@df6cdc0aa2637ff7>
MIME-Version 1.0
Content-Type text/plain; charset=utf-8
Content-Transfer-Encoding 8bit
Injection-Date Fri, 11 Sep 2026 10:50:18 +0000 (UTC)
Injection-Info dont-email.me; logging-data="2966685"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ba0/BzXYgitNM6kt+6h5f"; posting-host="5e8b773666f2baa1b3e9fe7abeba1530"
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Cancel-Lock sha1:+4byqaFY8gLrJ7P3LuSA/qw1dxQ= sha1:1Ei3TA8ZCxrEEELmN6hDeQJ1ygo= sha256:c7MfGgXAfVre8S3BxeePeJeNWlSldnwrxJSrxV4b7l4= sha1:FlZBGzLEJK/io9FWkjcOBteWHX0= sha256:BCoPzLC94DROPpGviTnnYuQa4fg7N6xvzaknni/urVQ=
Xref csiph.com comp.lang.forth:135658

Show key headers only | View raw

albert@spenarnc.xs4all.nl writes:
> If a word is optimised it is totally inlined.

As well as being a powerful optimization in its own right, I am guessing
that that opens up a lot of opportunities for the stack-manipulation-
annihilation optimization you were talking about in your previous post.

> [...]
>
> I got to the point that the original (unadulterated to favor
> a particular compiler) Byte benchmark performed in the league
> of mpe Forth.

That’s very impressive!

> I have 106 peephole patterns, some quite complicated.

How confident are you that all 106 are correct?

> [...]
> I decided to give up on i86 and concentrate on RISCV.

This kind of thing seems like it could be a significant advantage for
RISC-V, if people find that the cost-benefit ratio for writing compilers
for it is better than for 8086, i386, or amd64 (not sure which ISA you
meant by “i86”).

Kragen

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-01 10:49 +0200
  Re: First result in riscv optimiser anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-09-01 15:33 +0000
    Re: First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-01 18:54 +0200
    Re: First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-02 11:18 +0200
    Re: First result in riscv optimiser Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-04 13:14 -0300
      Re: First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-05 13:06 +0200
        Re: First result in riscv optimiser Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-08 02:21 -0300
          Re: First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-08 12:38 +0200
            Re: First result in riscv optimiser Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-11 07:50 -0300
              Re: First result in riscv optimiser Paul Rubin <no.email@nospam.invalid> - 2026-09-11 17:09 -0700
              Re: First result in riscv optimiser albert@spenarnc.xs4all.nl - 2026-09-13 14:03 +0200
            Re: First result in riscv optimiser antispam@fricas.org (Waldek Hebisch) - 2026-09-13 02:53 +0000

csiph-web