Re: Optimization techniques and runtime checks

On 07/05/2019 15:29, David Brown wrote:
> On 29/04/2019 22:36, Hans-Peter Diettrich wrote:


>> A better compiler could have a look at multiple (dependent) modules, so
>> that it can apply some more global optimizations during compilation
>> already.
>
> Indeed. And better compilers do that - it is known as "link time
> optimisation", "whole program optimisation", "omniscient optimisation",
> "inter-module optimisation", etc.


My recent compilers (not for C; the language doesn't really allow it)
have all been whole-program** compilers.


Although they don't really do optimisation (it's a separate project I
might get around to), they would be ideally placed as all the source
code is available for all functions at the same time.


There is one global, hierarchical symbol table linking all functions,
variables, types etc. across the project.


So anyway, thanks for confirming that mine might be one of the better
compilers! Usually you are not so kind.




(** The 'whole-program' is defined as all the source files that are
built into a single binary executable, or single shared library.


Functions in external libraries, which tend to be in another language
anyway, are not included in the source visible to the compiler. Such
libraries are also used only as shared libraries (eg. dll) so are never
statically linked.)

Return to the comp.compilers page.
Search the comp.compilers archives again.