Path: csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]
Date: Mon, 16 Sep 2024 12:16:09 -0700
Organization: A noiseless patient Spider
Lines: 5
Message-ID: <87cyl31kau.fsf@nightsong.com>
References: <nnd$61e0ad9a$48ed61c2@b4d945e456041481> <66d26c4b$1@news.ausics.net> <vaubf7$tbke$1@dont-email.me> <nnd$04cff141$0193ba04@301336b8dd8ed69a> <vbfqnd$v4c4$1@dont-email.me> <nnd$26b4d59b$27bdb181@ce638e508b04426e> <87bk0vbvgk.fsf@nightsong.com> <66e0fa58$1@news.ausics.net> <66e11d64$1@news.ausics.net> <877cbh4b6z.fsf@nightsong.com> <66e2a497$1@news.ausics.net> <2024Sep14.143207@mips.complang.tuwien.ac.at> <e29088cacf765cd0da6519e333fa78f1@www.novabbs.com> <2024Sep14.170836@mips.complang.tuwien.ac.at> <06f3574dfa63a100a731c944d8e16473@www.novabbs.com> <66e69759$1@news.ausics.net> <2407b32e4980726ab60611863c3d485e@www.novabbs.com> <19ef9c8626b9a9374535476f9073ad03@www.novabbs.com> <5631e74e91f46765ffe32945f12b748e@www.novabbs.com> <6e80829c88e569bb309120de17818b58@www.novabbs.com> <bc18049678801b31614fe87eba889a48@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Mon, 16 Sep 2024 21:16:10 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="d370c658a8af046045ee55fe02f3f136"; logging-data="3174560"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18D0swucqusZSZhWfaDe7aX"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:PRYosGWNCm7KHVrNCESUB9To7nA= sha1:kOhc8il8yMtihmuAZcCepj6FVeA=
Xref: csiph.com comp.lang.forth:132209

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.