Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: EuroForth 2025 preliminary proceedings Date: Sat, 17 Jan 2026 20:21:28 -0800 Organization: A noiseless patient Spider Lines: 9 Message-ID: <87sec3pn3r.fsf@nightsong.com> References: <69688c01$1@news.ausics.net> <2026Jan15.130413@mips.complang.tuwien.ac.at> <87wm1gpvdr.fsf@nightsong.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Sun, 18 Jan 2026 04:21:29 +0000 (UTC) Injection-Info: dont-email.me; posting-host="6b60582018677657191fc3d7babd9dec"; logging-data="3276325"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX186gWjDgaO+f0cF4gO/6c8a" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:SJ3hbiCNtDATe8G9FzLqbpi+0zM= sha1:ggevmHjjG+JGQrSW9STJ1bnED/s= Xref: csiph.com comp.lang.forth:134515 Hans Bezemer writes: > The tail call method however, requires an entirely different > VM. That's a lot of work for about 10% performance improvement - that > may not even last for a single GCC update. And requires two VM's to > maintain.. You'd have to change the VM but on the other hand, it's a documented and supported feature of both GCC and Clang, and other compilers might get it too. I wouldn't worry about it vanishing with the next GCC update.