Demo Data from EDBT 2026 / reviewers in the wild / expert
Manel Fernández
dblp:35/3102
· DBLP profile ↗
3ranked-venue papers
3as first author
0since 2021 · last 2004
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 3 · 3 first-author
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.
| Software engineering, system software, and programming languages
1 paper |
Program analysis · 87% Compilers and program optimization · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program analysis › data flow analysis
path-sensitive analysis |
0.0 | 1 | 2004 | Link-Time Path-Sensitive Memory Redundancy Elimination · HPCA 2004 |
Program analysis › static analysis
pointer analysis |
0.0 | 1 | 2004 | Link-Time Path-Sensitive Memory Redundancy Elimination · HPCA 2004 |
Compilers and program optimization › interprocedural optimization
link-time optimization |
0.0 | 1 | 2004 | Link-Time Path-Sensitive Memory Redundancy Elimination · HPCA 2004 |
Methods — techniques the papers use, named apart from their topics
path-sensitive analysis · 0.0alias analysis · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2004 | Link-Time Path-Sensitive Memory Redundancy EliminationabstractOptimizations performed at link-time or directly applied to final program executables have received increased attention in recent years. We discuss the discovery and elimination of redundant memory operations in the context of a link-time optimizer, an optimization that we call memory redundancy elimination (MRE). Previous research showed that existing MRE techniques are mainly based on path-insensitive information, which causes many MRE opportunities to be lost. We present a new technique for eliminating redundant loads in a path-sensitive fashion, by using a novel alias analysis algorithm that is able to expose path-sensitive memory redundancies. We also extend our previous work by removing both redundant and dead stores. Our experiments show that around 75% of load and 10% of store references in a program can be considered redundant, because they are accessing memory locations that have been referenced less than 256 memory instructions away. By combining our previous optimizations for eliminating load redundancies with the new techniques developed, we show that around 18% of the loads and 8% of the stores can be detected and eliminated, which translates into a 10% reduction in execution time. Manel Fernández, Roger Espasa |
HPCA | 1 |
| 2003 | Load redundancy elimination on executable codeabstractAbstract Optimizations performed at link time or directly applied to final program executables have received increased attention in recent years. This paper discusses the discovery and elimination of redundant load operations in the context of a link‐time optimizer, an optimization that we callLoad Redundancy Elimination (LRE). Our experiments show that between 50% and 75% of a program's memory references can be considered redundant because they are accessing memory locations that have been referenced less than 200–400 instructions away. We then present three profile‐based LRE algorithms targeted at optimizing away these redundancies. Our results show that between 5% and 30% of the redundancy detected can indeed be eliminated, which translates into program speedups of around 8%. We also test our algorithm assuming different cache latencies, and show that, if latencies continue to grow, the load redundancy elimination will become more important. Copyright © 2003 John Wiley & Sons, Ltd. Manel Fernández, Roger Espasa, Saumya K. Debray |
Concurr. Comput. Pract. Exp. | 1 |
| 2001 | Load Redundancy Elimination on Executable Code
Manel Fernández, Roger Espasa, Saumya K. Debray |
Euro-Par | 1 |