Deutsch English Français Italiano |
<v1qh7k$2ojd5$2@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thomas Koenig <tkoenig@netcologne.de> Newsgroups: comp.arch Subject: Re: Making Lemonade (Floating-point format changes) Date: Sun, 12 May 2024 13:46:28 -0000 (UTC) Organization: A noiseless patient Spider Lines: 27 Message-ID: <v1qh7k$2ojd5$2@dont-email.me> References: <abe04jhkngt2uun1e7ict8vmf1fq8p7rnm@4ax.com> Injection-Date: Sun, 12 May 2024 15:46:28 +0200 (CEST) Injection-Info: dont-email.me; posting-host="3165c36ec5f61794c7c042b567b915aa"; logging-data="2903461"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+zFq76M8QtbCdiF6DCzXWWSDAKF+X1E7E=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:1glb4R4AnSsh1KkNaTWNg/NFJlc= Bytes: 1804 John Savard <quadibloc@servername.invalid> schrieb: > I have instead defined a 256-bit format for floats which does not have > a hidden first bit, which looks like the old temporary reals, except > that the exponent field is one bit wider. Why not the IEEE binary256 (interchange) format? https://en.wikipedia.org/wiki/Octuple-precision_floating-point_format [...] >I've defined how the 256-bit internal format floats > can be doubled up to make a 512-bit float. Such floating point formats have very strange properties. For example, try defining epsilon so that 1.0+epsilon is the smallest number larger than 1.0... IBM just spent a lot of effort to move away from that for POWER. > I'm not really sure such floating-pont precision is useful, but I do > remember some people telling me that higher float precision is indeed > something to be desired. Well, the IEEE 754 standard has forced my > hand. How so?