this post was submitted on 06 Jan 2025
476 points (98.8% liked)

196

16798 readers
1795 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] user224@lemmy.sdf.org 42 points 3 days ago (1 children)
[–] smitten@lemmy.blahaj.zone 18 points 3 days ago* (last edited 3 days ago) (2 children)

Ah yes, the well known i5.90689059561

Edit: i5.90689059560851852932405837343720668462464580071706167251050905035703300440298377837242021827745839719063803418530941917054164942532445171041739

[–] user224@lemmy.sdf.org 7 points 2 days ago (1 children)

OK, I am dumb. Can you explain what that is?

[–] Tyfud@lemmy.world 22 points 2 days ago (1 children)

I'm not OP, but my guess is they're referring to the Intel math bug that some i5's had. I'm struggling to track it down, but it's basically an issue with doing long division where the floating point math would produce a very wrong result.

You can see more here at least for the bug/issue that existed in the 90's here

[–] smitten@lemmy.blahaj.zone 8 points 2 days ago (1 children)

I’m not actually, just that a binary integer that overflows at 60 couldn’t exist, hence the 5.907 whatever bit length

[–] Tyfud@lemmy.world 5 points 2 days ago (1 children)

oh, that's actually clever. And I'm saying that as a software engineer. I missed that possibility :)

[–] smitten@lemmy.blahaj.zone 3 points 2 days ago

I should have phrased it differently, like “Ah yes, the well known 5.9068905956 bit integer.” But thanks

[–] whostosay@lemmy.world 9 points 3 days ago

Is this what over-clocking is?