2018 IEEE International Symposium on High Performance Computer Architecture (HPCA) 2018
DOI: 10.1109/hpca.2018.00058
|View full text |Cite
|
Sign up to set email alerts
|

Lost in Abstraction: Pitfalls of Analyzing GPUs at the Intermediate Language Level

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
20
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 49 publications
(20 citation statements)
references
References 20 publications
0
20
0
Order By: Relevance
“…Prior work has shown how to use AMD's ROCm ecosystem to simulate HCC and HIP applications in gem5 with high fidelity compared to an AMD APU [5] [6]. In this work, we build from the existing ROCm support to simulate MI applications that use the MIOpen library [36].…”
Section: A the Gem5 Simulatormentioning
confidence: 99%
See 2 more Smart Citations
“…Prior work has shown how to use AMD's ROCm ecosystem to simulate HCC and HIP applications in gem5 with high fidelity compared to an AMD APU [5] [6]. In this work, we build from the existing ROCm support to simulate MI applications that use the MIOpen library [36].…”
Section: A the Gem5 Simulatormentioning
confidence: 99%
“…Although these tools could be used to perform similar studies, GPGPU-Sim focuses on discrete GPUs, not tightly coupled ones like gem5 models (GPGPU-Sim's recent updates could be integrated into gem5-gpu [34] to allow such a study). Moreover, recent work has shown that simulating at a higher level, like GPGPU-Sim, loses important architectural details and may lead to incorrect conclusions [5]. Thus, when combined with the importance of being able to recompile the libraries to run APU-compliant code, we believe gem5 and MIOpen represent the best combination between simulator and MI library.…”
Section: Pc-based L2 Bypassingmentioning
confidence: 99%
See 1 more Smart Citation
“…While Central Processing Unit (CPU) simulation techniques have reached maturity, GPU simulation often suffers from the following problems: (a) instruction sets are not accurately modeled, but approximated by an artificial, low-level intermediate representation [7], [8], (b) GPU simulators do not model existing commercial GPUs, but only simplified GPU architectures [9], (c) instead of using vendor provided driver stacks and compilers, GPU simulators often rely on simplified system software, which may behave entirely differently to original tools [10], [11], and (d) GPUs are treated as standalone devices, not modeling any CPU-GPU transactions [12]. This has led researchers using GPU simulation to rely on tools providing questionable accuracy [13]. For example, many existing GPU simulators including gem5-GPU [14], GpuTejas [15], Multi2Sim [10], GPGPU-Sim [16], and Multi2Sim-Kepler [11] claim cycle-accuracy.…”
Section: Introductionmentioning
confidence: 99%
“…GPU arithmetic cycles in the selected kernel differ by 47% (6.0 to 6.1). It is more than likely that simplified or non-vendor supplied tool chains used by other GPU simulators introduce even greater error, as also highlighted in [13].…”
Section: Introductionmentioning
confidence: 99%