Optimization order



Hi,

Do You Know Of Any Guidelines In Which Order Standard Compiler
Optimizations Should Be Invoked Promising Best Run-Time Results?

Probably, the order will vary from compiler to compiler due to
different implementations of the optimizations, but still I can
imagine that some types of optimizations might profit from other
optimization classes that should be invoked before.

Best regards,
Christian

.



Relevant Pages

  • Re: Optimization order
    ... Optimizations Should Be Invoked Promising Best Run-Time Results? ... the order will vary from compiler to compiler due to ... will find plenty of papers (sorry don't know the area well enough ...
    (comp.compilers)
  • Re: WaitForSingleObject() will not deadlock
    ... One is to hijack the semantics of volatile to disable compiler optimizations ... and otherwise let the compiler to agressive optimization. ... Agressive optimizations are the ones that work on the edge of the semantics of the ... Because the compiler can see into lock and unlock, it is able to reduce f ...
    (microsoft.public.vc.mfc)
  • Re: WaitForSingleObject() will not deadlock
    ... represent an incorrect implementation of the language. ... the *compiler* does not guarantee this. ... but to state it in terms of the execution instead of the formal semantics of the language ... as long as the optimizations do not change the semantics of the language). ...
    (microsoft.public.vc.mfc)
  • Re: optimized code
    ... > loop invariants are handled by the JIT not by the compiler fron-ends. ... generates the best optimized MSIL of any of the .NET languages. ... standard native code optimizations on MSIL code. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: c compilation - gcc vs visual c
    ... I recently compiled a numerically intensive c project under cygwin gcc ... MS focuses a lot more on specific optimizations, ... the simplest approach, however (and the one I currently use in my compiler), ... (silly code), are ones I focus on fixing. ...
    (comp.lang.c)