search for: tian2005

...ovided by Clang or another frontend or a some other mid-level IR. > 2) Optimizations are usually restricted by a single function boundary. > If procedurization is done in a front-end, this effectively kills any > optimizations – as simple ones as loop invariant code motion. Refer to > [Tian2005] for more information on why this is important for efficient > optimization of OpenMP programs. You're assuming all optimization is done by LLVM. That's not true in general. > It should be stressed, though, that in order to preserve correct > semantics of a user program, optimiz...

...atomics, lowering later may be better. > > > 2) Optimizations are usually restricted by a single function > > boundary. If procedurization is done in a front-end, this > > effectively kills any optimizations – as simple ones as loop > > invariant code motion. Refer to [Tian2005] for more information on > > why this is important for efficient optimization of OpenMP programs. > > You're assuming all optimization is done by LLVM. That's not true in > general. Even if LLVM has support for parallelization, no customer is required to use it. If you'...

...nd on source language; thus, it can be implemented once and used with any front-ends. 2) Optimizations are usually restricted by a single function boundary. If procedurization is done in a front-end, this effectively kills any optimizations – as simple ones as loop invariant code motion. Refer to [Tian2005] for more information on why this is important for efficient optimization of OpenMP programs. It should be stressed, though, that in order to preserve correct semantics of a user program, optimizations should be made thread-aware (which, to the best of our knowledge, is not the case with LLVM opti...

...it can > be implemented once and used with any front-ends. > > 2) Optimizations are usually restricted by a single function boundary. > If procedurization is done in a front-end, this effectively kills any > optimizations – as simple ones as loop invariant code motion. Refer to > [Tian2005] for more information on why this is important for efficient > optimization of OpenMP programs. > > It should be stressed, though, that in order to preserve correct > semantics of a user program, optimizations should be made thread-aware > (which, to the best of our knowledge, is not...

...t can > be implemented once and used with any front-ends. > > 2) Optimizations are usually restricted by a single function boundary. > If procedurization is done in a front-end, this effectively kills any > optimizations – as simple ones as loop invariant code motion. Refer to > [Tian2005] for more information on why this is important for efficient > optimization of OpenMP programs. > > It should be stressed, though, that in order to preserve correct > semantics of a user program, optimizations should be made thread-aware > (which, to the best of our knowledge, is no...

...t can > be implemented once and used with any front-ends. > > 2) Optimizations are usually restricted by a single function boundary. > If procedurization is done in a front-end, this effectively kills any > optimizations – as simple ones as loop invariant code motion. Refer to > [Tian2005] for more information on why this is important for efficient > optimization of OpenMP programs. > > It should be stressed, though, that in order to preserve correct > semantics of a user program, optimizations should be made thread-aware > (which, to the best of our knowledge, is no...