Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Ruby/Forth challenge for WJ Date: Tue, 12 Jan 2016 16:13:54 -0800 Organization: A noiseless patient Spider Lines: 9 Message-ID: <87si22mj3x.fsf@jester.gateway.pace.com> References: <35f4686c-f2c4-4ed8-9c46-2238645b9b97@googlegroups.com> <6e01edb6-e936-4418-bb77-e2ef9369a339@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="89fc4f87faf042e7e4d428a3639a51e3"; logging-data="21139"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19yjdsTujdLbtvZ/1WNx5uy" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:SMp/nv6dEK4a4IHjswswoZJPCxw= sha1:iucZj0nPs7sQo37525C9tb1zXA0= Xref: csiph.com comp.lang.forth:44806 peter.m.falth@gmail.com writes: > with my 64 bit token threaded forth I get 3092 ms on a 2 GHz i5 laptop > with my 32 bit native code generating forth I get 983 ms on the same laptop Interestingly, your 32 bit Forth is beating 64 bit C++ by a wide margin, even with C++ running on a considerably faster machine (i7-3770). That's using the std::array container straightforwardly: I'll see if I can fool with it to make it faster.