optimising compiler

(redirected from Compiler optimization)
Also found in: Wikipedia.

optimising compiler

(programming, tool)
compiler which attempts to analyse the code it produces and to produce more efficient code by performing program transformation such as branch elimination, partial evaluation, or peep-hole optimisation.

Contrast pessimising compiler.
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
References in periodicals archive ?
Topics discussed include context free grammars, recursive descent parsing, assembly language basics, JavaCC, compiler optimization, and interpreters.
Advanced Compiler Optimization Techniques, A Technical White Paper, Wind River, www.windriver.com, 2005.
In this section, we distinguish our work from others that address alias analysis, method resolution, and compiler optimization evaluation.
We begin our presentation with a review of background material related to compiler optimization. Then, we describe a study of the application of compiler analysis to derive the three block algorithms in LAPACK considered above from their corresponding point algorithms.
Incorporating theory and practical examples without delving too deeply into specific languages and syntax, the volume covers such topics as multi-core architectures, compiler optimization, parallel programming basics, node performance and accelerators.
Twenty-nine papers selected for the March 2006 symposium describe recent investigations on dynamic optimization, object-oriented code generation, phase detection and profiling, tiled and multicore compilation, and compiler optimization. Working in both academia and industry, the researchers present a code cache-aware interface to the Pin dynamic instrumentation system, space-efficient 64-bit Java objects, and an automated profiling approach to identify code locations whose executions correlate with phase changes.
In the design and implementation of programming languages, analysis is critical to compiler optimization and parallelization.
This could happen, for example, if the libraries are compiled using different compilers or compiler optimization levels.

Full browser ?