程序与编译器的组合优化方法.pptVIP

Responsible Pointer Usage Compiler alias analysis limits optimizations Developer knows App – tell compiler! Avoid pointing to same memory address with 2 different pointers Use array notation when possible Avoid pointer arithmetic if possible Pointer Disambiguation -Oa file.c (Windows) -fno-alias file.c (Linux) All pointers in file.c are assumed not to alias -Ow file.c (Windows) Not (yet) on Linux Assume no aliasing within functions (ie, pointer arguments are unique) -Qrestrict file.c (Windows) -restrict (Linux) Restrict Qualifier: Enables pointer disambiguation -Za file.c (Windows) -ansi (Linux) Enforce strict ANSI compilance (requires that pointers to different data types are not aliased) High Level Optimizations Available at O3 Prefetch Loop interchange Unrolling Cache blocking Unroll-and-jam Scalar replacement Redundant zero-trip elimination Data dependence analysis Reuse analysis Loop recovery Canonical expressions Loop fusion Loop distribution Loop reversal Loop skewing Loop peeling Scalar expansion Register blocking Data Prefetching Loop Interchange Note: c[i][j] term is constant in inner loop Interchange to allow unit stride memory access Unit Stride memory accessC/C++ Example – Fortran opposite Loop after interchange Note: a[i][k] term is constant in inner loop Two loads, one Store, one FMA: F/M = .33, Unit stride Unit Stride memory access (C/C++) Loop Unrolling Loop Unrolling - Candidates If trip count is low and known at compile time it may make sense to Fully unroll Poor Candidates: (similar issues for SWP or vectorizer) Low trip count loops – for (j=0; j N; j++) : N=4 at runtime Fat loops – loop body already has lots of computation taking place Loops containing procedure calls Loops with branches Loop Unrolling - Benefits Benefits perform more computations per loop iteration Reduces the effect of loop overhead Can increase Floating point to memory access ratio (F/M) Costs Register pressure Code bloat Loop Unrolling - Example All loop