Demo Data from EDBT 2026 / reviewers in the wild / expert
Richard K. Johnsson
dblp:61/5587
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 1982
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1 · 1 first-authorSoftware engineering, systems software and programming languages · 1 · 1 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 |
Programming languages and type systems · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Processor architecture and microarchitecture · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems
systems programming language |
0.0 | 1 | 1982 | An Overview of the Mesa Processor Architecture · ASPLOS 1982 |
Processor architecture and microarchitecture
instruction set architecture |
0.0 | 1 | 1982 | An Overview of the Mesa Processor Architecture · ASPLOS 1982 |
Methods — techniques the papers use, named apart from their topics
co-design of architecture, language and OS · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1982 | An Overview of the Mesa Processor ArchitectureabstractThis paper provides an overview of the architecture of the Mesa processor, an architecture which was designed to support the Mesa programming system [4]. Mesa is a high level systems programming language and associated tools designed to support the development of large information processing applications (on the order of one million source lines). Since the start of development in 1971, the processor architecture, the programming language, and the operating system have been designed as a unit, so that proper tradeoffs among these components could be made. Richard K. Johnsson, John D. Wick |
ASPLOS | 1 |