Object code optimizer: Difference between revisions

Revision as of 10:27, 4 July 2017

Revision as of 22:02, 12 February 2018

Line 1:

{{Multiple issues|

{{original research|date=November 2016}}

{{Confusing|reason=inconsistent}}

}}

[[Image:Binary optimizer.png|thumb|180px|A binary optimizer takes the existing output from a compiler and produces a better execution file with the same functionality.]]

An '''object code optimizer''', sometimes also known as a '''post pass optimizer''' or, for small sections of code, '''[[peephole optimization|peephole optimizer]]''', takes the output from a source language compile step - the object code or [[binary file]] - and tries to replace identifiable sections of the code with replacement code that is more [[algorithmic efficiency|algorithmically efficient]] (usually improved speed).