Demo Data from EDBT 2026 / reviewers in the wild / expert
Robert D. Clancy
dblp:238/2109
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2019
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Processor architecture and microarchitecture · 81% Memory systems · 19% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Processor architecture and microarchitecture
instruction fetch |
0.4 | 1 | 2019 | Elastic Instruction Fetching · HPCA 2019 |
Processor architecture and microarchitecture
branch prediction |
0.1 | 1 | 2019 | Elastic Instruction Fetching · HPCA 2019 |
Memory systems › cache › CPU cache
instruction cache |
0.1 | 1 | 2019 | Elastic Instruction Fetching · HPCA 2019 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2019 | Elastic Instruction FetchingabstractBranch prediction (i.e., the generation of fetch addresses) and instruction cache accesses need not be tightly coupled. As the instruction fetch stage stalls because of an ICache miss or back-pressure, the branch predictor may run ahead and generate future fetch addresses that can be used for different optimizations, such as instruction prefetching but more importantly hiding taken branch fetch bubbles. This approach is used in many commercially available high-performance design. However, decoupling branch prediction from instruction retrieval has several drawbacks. First, it can increase the pipeline depth, leading to more expensive pipeline flushes. Second, it requires a large Branch Target Buffer (BTB) to store branch targets, allowing the branch predictor to follow taken branches without decoding instruction bytes. Missing the BTB will also cause additional bubbles. In some classes of workloads, those drawbacks may significantly offset the benefits of decoupling. In this paper, we present ELastic Fetching (ELF), a hybrid mechanism that decouples branch prediction from instruction retrieval while minimizing additional bubbles on pipeline flushes and BTB misses. We present two different implementations that trade off complexity for additional performance. Both variants outperform a baseline decoupled fetcher design by up to 3.7% and 5.2%, respectively. Arthur Perais, Rami Sheikh, Luke Yen, Michael McIlvaine, Robert D. Clancy |
HPCA | 5 |