Demo Data from EDBT 2026 / reviewers in the wild / expert
Phil Nico
dblp:67/6484
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1993
—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 · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Processor architecture and microarchitecture
branch prediction |
0.0 | 1 | 1993 | A comparision of superscalar and decoupled access/execute architectures · MICRO 1993 |
Processor architecture and microarchitecture
instruction fetch |
0.0 | 1 | 1993 | A comparision of superscalar and decoupled access/execute architectures · MICRO 1993 |
Processor architecture and microarchitecture
superscalar processor |
0.0 | 1 | 1993 | A comparision of superscalar and decoupled access/execute architectures · MICRO 1993 |
Processor architecture and microarchitecture › execution model
decoupled access/execute architecture |
0.0 | 1 | 1993 | A comparision of superscalar and decoupled access/execute architectures · MICRO 1993 |
Methods — techniques the papers use, named apart from their topics
trace-driven simulation · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1993 | A comparision of superscalar and decoupled access/execute architecturesabstractEven with a very accurate dynamic branch predictor, a superscalar processor must predict instruction fetch addresses no later than the first pipeline stage to avoid suffering pipeline bubbles every time a branch is taken. Unfortunately, branch addresses generally are not known prior to instruction decode. Therefore, some indirect technique is required to identify a branch instruction and enable branch prediction while the branch instruction is being fetched. This is the branch identification problem. Intel Pentium adopts a scheme that solves this problem; however, its scheme assumes an issue rate of two instructions per cycle. An aggressive superscalar processor, issuing more than two instructions per cycle, cannot effectively use that scheme. The authors propose and compare two viable schemes for solving the branch identification problem for wide-issue superscalar processors.> Matthew K. Farrens, Pius Ng, Phil Nico |
MICRO | 3 |