Sujet : Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]
De : jan4comp.lang.forth (at) *nospam* murray-microft.co.uk (Jan Coombs)
Groupes : comp.lang.forthDate : 13. Sep 2024, 13:07:32
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240913130732.06c11152@t530>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Claws Mail 4.1.1 (GTK 3.24.38; x86_64-pc-linux-gnu)
On Fri, 13 Sep 2024 03:38:51 -0700
Paul Rubin <
no.email@nospam.invalid> wrote:
I would say that the claim of better performance from locals depends
on the implementation[...]
Absolutely. As Chucks prime target of interest (hardware) uses LIFO
registers for stacks, only the top top one, or so, R stack items could
be used for restricted local storage (which is also common practice).
I accept that locals are useful, and would like to see hardware stack
engine implementations that support this better while retaining the
performance advantage of a stack cache implemented as LIFO registers
rather than in RAM.
Jan Coombs
--