Sujet : Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]
De : mhx (at) *nospam* iae.nl (mhx)
Groupes : comp.lang.forthDate : 16. Sep 2024, 22:43:13
Autres entêtes
Organisation : novaBBS
Message-ID : <930672243542a2e04c6cd13d83108af9@www.novabbs.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
User-Agent : Rocksolid Light
On Mon, 16 Sep 2024 19:16:09 +0000, Paul Rubin wrote:
mhx@iae.nl (mhx) writes:
This appears not to be a good idea. The root cause is piling up too
many items on the F-stack (exceeding the hardware FPU stack limits).
>
I wonder if any Forth compilers use SSE instead of the x86 FPU stack.
iForth would, if my tests had showed any positive effect.
(The effect has to be substantial to outweigh the advantage of 80-bit
floats whenever accuracy counts.)
I wrote routines to process 4 floats. For unfathomable reasons, they
are not nearly as good a pre-packaged library code. There is only
limited potential for standard FP code to benefit from SSE. If
parallelism can't be exploited, SSE does not seem to bring
anything over the old FPU. But maybe my hardware was not
good enough a few years back.
With SSE I need a substantial library for special functions,
which then become relatively slow DLL calls.
The only thing wrong with the FPU is that the special stack
overflow interrupts don't work.
-marcel