Floating-point arithmetic: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

25 August 2025

7 August 2025

19 July 2025

  • curprev 17:3317:33, 19 July 2025 Vincent Lefèvre talk contribs 123,654 bytes +14 Incidents: Though the issue did not come from floating point, it is still due to the careless use of approximations: if they had use an exact arithmetic (thus not needing to approximate 0.1) or wrote their code based on an error analysis, this would not have happened. undo

17 July 2025

9 July 2025

  • curprev 11:3011:30, 9 July 2025 Vincent Lefèvre talk contribs 123,336 bytes −146 Incidents: The intent is that there is a single time unit: 0.1s. The issue is that the software assumed that its accuracy did not matter; Skeel says: "this time difference should be in error by only 0.0001%, a truly insignificant amount". Something that may remain true... until a cancellation occurs like here. undo
  • curprev 01:1201:12, 9 July 2025 Taylor Riastradh Campbell talk contribs 123,482 bytes +957 Incidents: Clarify what happened with the Patriot missile battery, which was, despite popular wisdom, not caused by using floating-point, but rather by using two different unit conversions that disagreed, with a discrepancy that increased with uptime. undo

30 June 2025

20 June 2025

15 June 2025

9 June 2025

8 April 2025

5 April 2025

4 April 2025

3 April 2025

27 March 2025

26 March 2025

12 March 2025

11 March 2025

26 February 2025

29 January 2025

28 January 2025

24 January 2025

11 January 2025

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)