Revision as of 03:34, 19 November 2016 edit Dgpop (talk \| contribs) Extended confirmed users 57,675 edits original research ← Previous edit		Revision as of 09:50, 4 July 2017 edit undo Matthiaspaul (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors 137,876 edits →Other optimizers: Removed UPX as there are dozens of other exe compressors as well. Not sure if exe compression would count as "binary optimization" at all Next edit →
Line 12: ===Other optimizers=== Some binary optimizers ~~such as [[UPX]]~~ do [[executable compression]], which reduces the ''size'' of binary files using generic [[data compression]] techniques, reducing storage requirements and transfer and loading times, but not improving run-time performance. Actual consolidation of duplicate library modules would also reduce memory requirements. Some binary optimizers utilize [[run time (program lifecycle phase)\|run-time]] metrics ([[profiling (computer programming)\|profiling]]) to introspectively improve performance using techniques similar to [[just-in-time compilation\|JIT]] compilers.

Object code optimizer: Difference between revisions