CodeCompositionExpensive
Revision as of 14:31, 18 March 2019 by Thomas-gruber-5537@uni-erlangen.de (talk | contribs)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
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