#floatingpoint

रञ्जित (Ranjit Mathew)rmathew
2026-02-21

Another excellent post 👌🏽 from Russ Cox 👇🏽🫡:

“Floating-Point Printing And Parsing Can Be Simple And Fast” (research.swtch.com/fp).

On HN: news.ycombinator.com/item?id=4

On Lobsters: lobste.rs/s/nbsclr/floating_po

Johnny's Software Labjohnnysswlab@mastodon.online
2026-02-18

🚀 New on Johnny’s Software Lab: Handling floating-point errors in C++ without killing performance!
NaNs, infinities, sticky bits, and traps — what works and what’s a trap 🪤.

Read more: johnnysswlab.com/floating-poin

#Cpp #Performance #FloatingPoint #NaN #Infinity

2026-02-06

Learn about numeric data types (and the number 998,001) in Python

The value 1 / 998,001 has an interesting property, but to see it in Python you need to learn about numeric data types.

rodstephensbooks.com/many_digi

#Python #FloatingPoint #Decimal #Precision

The value 1 / 998001 produces a sequence of every three-digit number from 000 to 999 in order except 998
2026-02-05

Проектирование FPU блока, работающего на частоте 7 ГГц

Данный проект представляет собой современный вычислительный блок, предназначенный для обработки научных и графических данных на сверхвысокой частоте 7 ГГц . Архитектура построена на базе 128-битных векторов и 5-стадийного конвейера.

habr.com/ru/articles/993270/

#floatingpoint #floating_point

[[Russ Cox] 부동 소수점 변환의 혁신: 더 쉽고, 더 빠르며, 더 간단하게

Russ Cox가 제안한 새로운 부동 소수점 변환 알고리즘은 기존 알고리즘보다 단순하고 성능이 뛰어납니다. 'Unrounded Scaling'이라는 핵심 프리미티브를 통해 2진수와 10진수 변환을 가속화하며, Go 1.27에 포함될 예정입니다.

news.hada.io/topic?id=26107

#floatingpoint #algorithm #performance #go #unroundedscaling

JavaScriptBuzzJavaScriptBuzz
2026-01-14

How to Stop Floating Point Money Bugs

0.1 + 0.2 is not 0.3 in JavaScript.

youtube.com/watch?v=cCvDtsba810

JavaScriptBuzzJavaScriptBuzz
2025-12-09

0.1 + 0.2 = 0.30000000000000004?!

JavaScript math is broken! Adding 0.1 + 0.2 creates a number that will shock you. This is why financial apps fail! Watch the chaos!

youtube.com/shorts/MC2ipBoctZo

2025-12-07

#DecemberAdventure 7th

found+fixed a #bug : part of one track was using single precision float instead of double in one critical segment; it worked ok at 48kHz sample rate but at 96kHz it reached #FloatingPoint precision limits leading to a counter failing to increment past a certain point, meaning the track end condition was never reached...

R.L. Dane :Debian: :OpenBSD: :FreeBSD: 🍵 :MiraLovesYou:rl_dane@polymaths.social
2025-12-03
Nils Goroll 🕊️slink@fosstodon.org
2025-12-03
Dyalogdyalog
2025-11-17

2013-07: Write a function that selects the floating point (non-integer) numbers from a numeric vector (see apl.quest/2013/7/ to test your solution and view ours).

2025-11-16

did some minor hacking on #Fraktaler3 today for the first time in months.

- fixed it so it works with toml11 v4 (run "make") as well as v3 (run "make TOML11=3")

- removed "quit when done" checkbox from android and web builds, where it doesn't make sense

- fix: correct status is now shown when pressing ESC after the rendering is complete

- added double precision version of floatexp (separate floating point mantissa and integer exponent, for wider dynamic range necessary for very deep zooms); the extra precision of doubleexpover single precision floatexp turns out to be necessary sometimes (more often with higher power formulas and higher iteration counts)

- fixed the mildly bitrotted quadruple precision float128 support, now works again enabled (run "make") and disabled (run "make FLOAT128="). hopefully it won't be necessary to use it for more than checking that double precision image are plausible, because it's very slow.

#fractals #DeepZoom #FloatingPoint

dialog comparing different floating point number type implementations.

columns from left to right:

type; mantissa bits; exponent bits; speed on CPU (AMD 2700X); speed on GPU (AMD RX 580)

the speeds are logarithmic: an increment of one unit corresponds to half the time taken.

the fastest is float on GPU, speed 22.38, which is 777x faster than the slowest, float128 on CPU with speed 12.78
2025-11-05

Nên sử dụng số thập phân thay cho số浮 điểm trong ngôn ngữ lập trình cấp cao. Số浮 điểm nhanh nhưng có hạn chế, trong khi phần cứng hiện đại đã giải quyết vấn đề hiệu suất. Sử dụng số thập phân chính xác có thể tiết kiệm thời gian và công sức cho lập trình viên. #LậpTrình #NgônNgữLậpTrình #SốThậpPhân #SốFloat #HiệuSuất #LậpTrìnhCấpCao #Programming #FloatingPoint #ArbitraryPrecisionArithmetic

reddit.com/r/programming/comme

2025-11-05

Nên thay đổi số mặc định trong ngôn ngữ lập trình cấp cao: không nên sử dụng số thực mà nên sử dụng số thập phân chính xác. u điểm của số thực là nhanh, nhưng hạn chế lớn là không chính xác. #LậpTrình #NgônNgữLậpTrình #SốThực #SốThậpPhân #Programming #FloatingPoint #Arithmetic

reddit.com/r/programming/comme

amanjeev | امن جیو | ਅਮਨਜੀਵamanjeev@cosocial.ca
2025-11-01

watch me improve my approximate revelry. watch me double the precision of my gloating point.

#astoot #floatingpoint

@linuxgal

Note that this isn't Python-specific behaviour. This is required by the IEEE-754 floating-point standard, which Python (and most other runtimes) conform to.

NaN, Inf, -Inf, comparison rules, exceptions ... it's all in there.

#Python #IEEE754 #FloatingPoint #math #standard

vyvy
2025-10-31

What kind of mishegus is this?
"There are ARM processors that have mixed-endian floating-point representation for double-precision numbers: each of the two 32-bit words is stored as little-endian, but the most significant word is stored first."

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst