Multi-Threshold Voltage (Multi-Vt)
How libraries offer the same cells at several threshold voltages, and how mixing high, standard and low Vt trades leakage for speed.
A standard cell library usually comes in several threshold voltage (Vt) flavours with the same functions, footprints and pins. A NAND2 exists as a high-Vt, a standard-Vt and a low-Vt version, and often an ultra-low-Vt one too. Multi-Vt optimisation uses slow, low-leakage cells wherever timing allows and fast, leaky cells only where it must.
The physics in two sentences
A transistor that is off still conducts a small subthreshold current, and that current falls exponentially as the threshold voltage rises: roughly ten times less leakage for every 70 to 100 mV of extra Vt at room temperature. A higher Vt also leaves less gate overdrive (V minus Vt), so the transistor switches more slowly.
So the trade is lopsided in your favour: a high-Vt cell might be 20 to 40% slower but leak ten times less. Most paths in a design have spare slack, so most cells can afford to be slow.
The flavours
Exact numbers depend on the process and library. The ratios below are illustrative and relative to an LVT cell.
| Flavour | Relative delay | Relative leakage | Typical use |
|---|---|---|---|
| HVT (high Vt) | ≈1.3-1.4× | ≈0.05-0.1× | The default for most logic with slack |
| SVT / RVT (standard) | ≈1.1-1.2× | ≈0.2-0.3× | Moderately critical paths |
| LVT (low Vt) | 1.0× | 1.0× | Critical paths only |
| ULVT (ultra-low Vt) | ≈0.85-0.9× | ≈3-5× | The few paths nothing else can close |
Because the flavours share footprints, swapping one for another is a legal change at any stage, even after routing. That makes Vt swapping one of the cheapest timing and leakage ECOs there is. At FinFET nodes, libraries often add a second knob, channel length variants, which trade speed for leakage in the same way.
Worked example: leakage recovery
A block of 200,000 cells, all SVT, leaks 10 mW at the hot corner. After timing analysis, 80% of the cells turn out to have enough slack to become HVT, which in this library leaks four times less. Closing a few critical paths needs 5% of the cells to become LVT, which leaks four times more than SVT.
All SVT: 10.0 mW
80% → HVT: 0.80 × 10 mW / 4 = 2.0 mW
15% stay SVT: 0.15 × 10 mW = 1.5 mW
5% → LVT: 0.05 × 10 mW × 4 = 2.0 mW
Total = 5.5 mW (45% less leakage)
Note that the 5% of LVT cells leak as much as all 80% of HVT cells.
Every LVT cell has to earn its place.The flow
- Synthesis starts from HVT and SVT cells, with LVT restricted or capped, so the tool uses fast cells only where the netlist cannot meet timing otherwise.
- Place and route optimisation may swap cells to faster flavours to fix timing after real wire delays appear.
- After routing, a signoff ECO pass (for example PrimeTime fix_eco_power) swaps every cell that has spare slack back to a lower-leakage flavour, checked against all timing corners.
- Leakage is signed off at the worst leakage corner, usually fast process and high temperature.
# Design Compiler: cap the share of low-Vt cells
set_attribute [get_libs *lvt*] default_threshold_voltage_group LVT -type string
set_multi_vth_constraint -lvth_groups {LVT} -lvth_percentage 5
compile_ultra
report_threshold_voltage_group
# PrimeTime (signoff ECO): trade slack for leakage on every corner
fix_eco_power -pattern_priority {HVT SVT LVT}
write_changes -format icctcl -output vt_swap.tclA good design has a healthy majority of HVT cells and a small LVT share. When you see a block with 40% LVT, that is a sign timing was closed with brute force, and leakage will show it. Interviewers like the phrase "use the highest Vt that still meets timing".
Hold timing works the other way. Swapping a cell to HVT slows the path, which helps hold, but swapping to LVT to fix setup can create hold violations on short paths that share the cell. Always re-check hold at the fast corner after Vt changes.
Finished reading?
Mark it complete to track your progress through the path.
Go further
Prepare the low-power and physical design answers interviewers expect.
Get new lessons by email
New lessons, interview prep and real EDA tool workflows. No spam.