| Deutsch English Français Italiano |
|
<2d6811168025a74b3ff51a78efb75947d36a0146@i2pn2.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: dxf <dxforth@gmail.com> Newsgroups: comp.lang.forth Subject: Re: Parsing timestamps? Date: Sun, 13 Jul 2025 21:28:43 +1000 Organization: i2pn2 (i2pn.org) Message-ID: <2d6811168025a74b3ff51a78efb75947d36a0146@i2pn2.org> References: <1f433fabcb4d053d16cbc098dedc6c370608ac01@i2pn2.org> <2025Jul10.094723@mips.complang.tuwien.ac.at> <87h5zjx2lb.fsf@nightsong.com> <mdaotaF7ghoU1@mid.individual.net> <5c41bdca5cae4d9cb47948a87e670c2ffc5f1233@i2pn2.org> <878qkvwh3w.fsf@nightsong.com> <cdf19da4f12fb2871cb316a7da47561e139b640a@i2pn2.org> <874ivjw48w.fsf@nightsong.com> <91e8859d9cb678b7ce7a8a5f341de513@www.novabbs.com> <2025Jul11.122254@mips.complang.tuwien.ac.at> <954cf34891bed0677fd79af0b676c50613dc1443@i2pn2.org> <2025Jul13.110141@mips.complang.tuwien.ac.at> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Date: Sun, 13 Jul 2025 11:28:45 -0000 (UTC) Injection-Info: i2pn2.org; logging-data="430415"; mail-complaints-to="usenet@i2pn2.org"; posting-account="XPw7UV90Iy7EOhY4YuUXhpdoEf5Vz7K+BsxA/Cx8bVc"; User-Agent: Mozilla Thunderbird In-Reply-To: <2025Jul13.110141@mips.complang.tuwien.ac.at> X-Spam-Checker-Version: SpamAssassin 4.0.0 Content-Language: en-GB On 13/07/2025 7:01 pm, Anton Ertl wrote: > ... > For Forth, Inc. and MPE AFAIK their respective IA-32 Forth system was > the only one with hardware FP for many years, so there probably was > little pressure from users for bit-identical results with, say, SPARC, > because they did not have a Forth system that ran on SPARC. What do you mean by "bit-identical results"? Since SSE2 comes without transcendentals (or basics such as FABS and FNEGATE) and implementers are expected to supply their own, if anything, I expect results across platforms and compilers to vary. > ... > And as long as customers did not ask for bit-identical results to > those on, say, a Raspi, there was little reason to reimplement FP with > SSE2. I wonder if the development of the SSE2 package for VFX was > influenced by the availability of VFX for the Raspi. According to the change log it originally began as software floating point for embedded systems and circa 2020 was converted to SSE and x64. Perhaps Stephen can advise as to the reasons. > > These Forth systems also don't do global register allocation or > auto-vectorization, so two other reasons why, e.g., C compilers chose > to use SSE2 on AMD64 (where SSE2 was guaranteed to be available) don't > exist for them. > > - anton