Integer overflow: Difference between revisions

Revision as of 04:22, 28 August 2021

Revision as of 09:52, 17 October 2021

Line 122:

===Handling===

If it is anticipated that overflow may occur, then tests can be inserted into the program to detect when it happens, or is about to happen, and do other processing to mitigate it. For example, if an important result computed from user input overflows, the program can stop, reject the input, and perhaps prompt the user for different input, rather than the program proceeding with the invalid overflowed input and probably malfunctioning as a consequence. This full process can be automated: it is possible to automatically synthesize a handler for an integer overflow, where the handler is for instance a clean exit.<ref>{{Cite journal|last1=Muntean|first1=Paul Ioan|last2=Monperrus|first2=Martin|last3=Sun|first3=Hao|last4=Grossklags|first4=Jens|last5=Eckert|first5=Claudia|date=2019|title=IntRepair: Informed Repairing of Integer Overflows|journal=IEEE Transactions on Software Engineering|volume=47|issue=10|pages=12225–2241|doi=10.1109/TSE.2019.2946148|issn=0098-5589|arxiv=1807.05092|s2cid=51627444}}</ref>

[[Central processing unit|CPUs]] generally have a way of detecting this to support addition of numbers larger than their register size, typically using a status bit; the technique is called multiple-precision arithmetic.