CodeCompositionExpensive

From HPC Wiki
Revision as of 15:17, 3 September 2019 by Daniel-schurhoff-de23@rwth-aachen.de (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Description

The pattern "Code composition - expensive instructions" can be used to describe what happens if you use expensive instructions although there are cheaper ways.

Symptoms

Like Instruction Overhead.

For a piece of high-level code, the compiler outputs a lot of instructions although is could be done in less. One common example are non-vectorized instructions.


Detection

High CPI if the problem is large-latency arithmetic


Possible optimizations and/or fixes

Reduce complexity to that the compiler can generate better code


Applicable applications or algorithms or kernels