Bots, Bureaucrats, Interface administrators, smwadministrator, smwcurator, smweditor, Administrators
2,557
edits
Loop Unrolling Transformation: Difference between revisions
Jump to navigation
Jump to search
→Loop Unrolling in C/C++ Compilers
Timo.stripf (talk | contribs) |
Timo.stripf (talk | contribs) |
||
| Line 15: | Line 15: | ||
In addition to automatic unrolling, developers can explicitly influence unrolling behavior through compiler-specific pragmas. These pragmas allow developers to: | In addition to automatic unrolling, developers can explicitly influence unrolling behavior through compiler-specific pragmas. These pragmas allow developers to: | ||
* Force a specific unroll factor. | |||
* Disable unrolling for performance or code size reasons. | |||
* Request full unrolling for small loops. | |||
Compiler pragmas for unrolling provide fine-grained control over how loops are transformed, which is useful when compiler heuristics do not align with application-specific performance goals. For example, manually unrolling cache-sensitive loops can improve data locality, while avoiding unrolling in some cases can reduce code bloat. | Compiler pragmas for unrolling provide fine-grained control over how loops are transformed, which is useful when compiler heuristics do not align with application-specific performance goals. For example, manually unrolling cache-sensitive loops can improve data locality, while avoiding unrolling in some cases can reduce code bloat. | ||