CPU Design · All levels

Branch Prediction Basics

Fetch & Decode Front-End: Direction and target predictors speculate next fetch PC to keep the pipeline full; every wrong-path episode burns cycles by flushing decode/rename work and refilling from correct control flow.

What this topic teaches

Branch Prediction Basics turns CPU design theory into actionable review decisions. Direction and target predictors speculate next fetch PC to keep the pipeline full; every wrong-path episode burns cycles by flushing decode/rename work and refilling from correct control flow. The target is evidence-backed closure, not opinion-driven tuning.

Senior-engineer framing question

When branch MPKI, prediction accuracy, and fetch redirection penalty cycles shifts, can you prove first failing stage, dominant mechanism, accountable owner, and release-safe mitigation?

diagram

CPU PIPELINE VIEW - Branch Prediction Basics

fetch -> decode -> rename -> dispatch -> execute -> retire
  |        |         |          |         |         |
icache   uop flow   map table  queueing  FU ports  ROB commit

steady-state goal:
keep every stage supplied without bubbles or flush storms

Focus: connect metric movement to the first stage loss
Metric tracked: branch MPKI, prediction accuracy, and fetch redirection penalty cycles

Architecture visuals

Draw the mechanism before changing knobs. These visuals are optimized for design reviews and interview whiteboards.

Prediction and redirect loop

diagram

BRANCH PREDICTOR VIEW - Branch Prediction Basics

fetch PC -> BTB lookup -> direction predictor -> target select -> fetch redirect
               |               |                    |
          BTB miss cost     confidence         RAS / indirect path

branch resolves in execute:
correct prediction  -> pipeline keeps flowing
mispredict          -> flush + restart + refill

Focus: show direction and target mistakes that trigger wrong-path fetch

Prediction regression triage tree

diagram

ROOT-CAUSE TREE - Branch Prediction Basics

branch MPKI, prediction accuracy, and fetch redirection penalty cycles regressed
        |
  reproducible on fixed seed?
      /               \
    no                 yes
    |                   |
env/tool drift      first failing stage?
                    /        |        \
                front-end   execute   memory/system
                   |          |            |
              fetch/decode   port/ROB   cache/TLB/NoC

Stop at first confirmed mechanism, then patch with owner accountability.

Out-of-order control map

diagram

OOO CORE BLOCK DIAGRAM - Branch Prediction Basics

decode -> rename -> dispatch -> reservation stations -> execute units
             |                        |                    |
       free-list / map table       wakeup-select         writeback
             \                        |                    /
              +-------- reorder buffer / retire ---------+

Focus: rename to retire dataflow

Memory hierarchy map

diagram

CPU CACHE + MEMORY HIERARCHY - Branch Prediction Basics

                 [ L1I ]   [ L1D ]
               32-64KB, ~4 cycles
                      \     /
                       [  L2  ]
                 512KB-2MB, ~12 cycles
                           |
                         [ L3 ]
               shared LLC, 30-60 cycles
                           |
                    [ DDR/HBM memory ]
                    80-150ns effective

Optimization lens: latency vs capacity tradeoff

Speculation lens

diagram

BRANCH PREDICTOR VIEW - Branch Prediction Basics

fetch PC -> BTB lookup -> direction predictor -> target select -> fetch redirect
               |               |                    |
          BTB miss cost     confidence         RAS / indirect path

branch resolves in execute:
correct prediction  -> pipeline keeps flowing
mispredict          -> flush + restart + refill

Focus: minimize wrong-path work

Ownership layers

diagram

CPU OWNERSHIP LAYERS - Branch Prediction Basics

artifact area     owner
----------------  ----------------------------
architecture    branch predictor owner
RTL/microarch   front-end RTL owner
software/tools  performance analyst

Rule: every regressed metric must map to an explicit owner and closure artifact.

Evidence required

Primary metric: branch MPKI, prediction accuracy, and fetch redirection penalty cycles.
Primary artifact: predictor confusion matrix, BTB hit/miss log, and redirect trace.
Owners to include: branch predictor owner, front-end RTL owner, performance analyst.
One reproducible failing workload and one stable comparator run.
One run with fully locked environment metadata for causal comparison.

Compute-memory limit lens

diagram

CPU ROOFLINE - Branch Prediction Basics

performance
   ^
   |                 compute roof
   |                /
   |               /
   |--------------/---------------- memory roof
   +----------------------------------------------> arithmetic intensity
      memory-bound                 compute-bound

Interpretation: separate compute and memory limits

Key takeaways

Classify stage loss before proposing fixes.
Use artifacts to separate mechanism from symptoms.
Close with owner accountability and rollback criteria.

Common pitfalls

Using average IPC alone while ignoring tail behavior.
Comparing traces across mismatched binaries or thermal states.
Calling closure without workload-level validation.

CPU deep dive

Front-end quality is proven by sustained rename feed under branchy and translation-heavy instruction streams.

Concept diagram

diagram

FRONT-END FLOW

I-cache/ITLB -> branch predict -> fetch queue -> decode/uOP cache -> rename

Metric graph

diagram

FRONT-END BOTTLENECK MIX

predictor redirects   █████
ITLB + I-cache stalls ████
decode backpressure   ███

Reports and artifacts

fetch bandwidth timeline
branch redirection profile
uOP cache hit/miss report
front-end bubble taxonomy

Mini case study

A code-layout change increased branch target aliasing; fetch redirect penalties doubled and retire IPC dropped 18%.

Debug branches

Correlate MPKI spikes with queue underflow windows
Audit decode throughput versus uOP-cache residency
Confirm front-end fixes improve full CPI stack, not only fetch counters

Senior review question

Ask: which CPI/latency evidence proves this topic is truly closed beyond synthetic benchmarks?

Key takeaways

Always connect microarchitectural counter changes to product workload outcomes.
Lock binary, compiler, firmware, and thermal metadata before comparing CPU traces.

Common pitfalls

Treating average IPC as sufficient proof while ignoring latency tails and outliers.
Applying predictor or prefetch tweaks without first-failing-stage attribution.
Declaring closure without reproducible perf, correctness, and power gates.

Practice this lesson