EDBT 2026 Demo / reviewers in the wild / expert
Alan Eustace
dblp:06/3094
· DBLP profile ↗
3ranked-venue papers
1as first author
0since 2021 · last 1997
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 2 · 1 first-authorSoftware engineering, systems software and programming languages · 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.
| Software engineering, system software, and programming languages
2 papers |
Compilers and program optimization · 48% Program analysis · 34% Runtime systems and virtual machines · 18% |
Topics — the 7 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Runtime systems and virtual machines
dynamic compilation |
0.0 | 1 | 1997 | Value Profiling · MICRO 1997 |
Compilers and program optimization › dynamic optimization
profile-guided optimization |
0.0 | 1 | 1997 | Value Profiling · MICRO 1997 |
Compilers and program optimization
program specialization |
0.0 | 1 | 1997 | Value Profiling · MICRO 1997 |
Program analysis › dynamic analysis › profiling
value profiling |
0.0 | 1 | 1997 | Value Profiling · MICRO 1997 |
Program analysis
program analysis infrastructure |
0.0 | 1 | 1994 | ATOM - A System for Building Customized Program Analysis Tools · PLDI 1994 |
Compilers and program optimization
program instrumentation |
0.0 | 1 | 1994 | ATOM - A System for Building Customized Program Analysis Tools · PLDI 1994 |
Program analysis
dynamic analysis |
0.0 | 1 | 1994 | ATOM - A System for Building Customized Program Analysis Tools · PLDI 1994 |
Methods — techniques the papers use, named apart from their topics
profiling · 0.0convergent profiling · 0.0code instrumentation · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1997 | Value ProfilingabstractIdentifying variables as invariant or constant at compile-time allows the compiler to perform optimizations including constant folding, code specialization, and partial evaluation. Some variables, which cannot be labeled as constants, may exhibit semi-invariant behavior. A semi-invariant variable is one that cannot be identified as a constant at compile-time, but has a high degree of invariant behavior at run-time. If run-time information was available to identify these variables as semi-invariant, they could then benefit from invariant-based compiler optimizations. We examine the invariance found from profiling instruction values, and show that many instructions have semi-invariant values even across different inputs. We also investigate the ability to estimate the invariance for all instructions in a program from only profiling load instructions. In addition, we propose a new type of profiling called convergent profiling. Estimating the invariance from loads and convergent profiling are used to reduce the profiling time needed to generate an accurate value profile. The value profile can then be used to automatically guide code generation for dynamic compilation, adaptive execution, code specialization, partial evaluation and other compiler optimizations. Brad Calder, Peter Feller, Alan Eustace |
MICRO | 3 |
| 1995 | ATOM: A Flexible Interface for Building High Performance Program Analysis Tools
Alan Eustace, Amitabh Srivastava |
USENIX | 1 |
| 1994 | ATOM - A System for Building Customized Program Analysis ToolsabstractATOM (Analysis Tools with OM) is a single framework for building a wide range of customized program analysis tools. It provides the common infrastructure present in all code-instrumenting tools; this is the difficult and time-consuming part. The user simply defines the tool-specific details in instrumentation and analysis routines. Building a basic block counting tool like Pixie with ATOM requires only a page of code. Amitabh Srivastava, Alan Eustace |
PLDI | 2 |