Difference between revisions of "CodeCompositionExpensive"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| + | [[Category:Performance Pattern]] | ||
== Description == | == Description == | ||
The pattern "Code composition - expensive instructions" can be used to describe what happens if you use expensive instructions although there are cheaper ways. | The pattern "Code composition - expensive instructions" can be used to describe what happens if you use expensive instructions although there are cheaper ways. | ||
Latest revision as of 16:17, 3 September 2019
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