It doesn't actually sound like he "solved" it. More like he put error bounds around it and can detect when the error is more than X. > When the calculated resu

It doesn't actually sound like he "solved" it. More like he put error bounds around it and can detect when the error is more than X. > When the calculated result is no longer sufficiently accurate the result is so marked, as are all further calculations made using that value. Solving it would be a pretty big deal. This doesn't feel like it is, though I admit I haven't worked on a similar problem in a long time. Kinda feels like patent trolling as I imagine that lots of companies have put bounds on detecting floating point errors when they need it. There are certainly lots of papers on it: https://www.google.com/search?q=floating+point+error+bounds https://www.google.com/search?q=floating+point+error+bounds