2016
DOI: 10.1007/978-3-319-45550-1_20
|View full text |Cite
|
Sign up to set email alerts
|

Early Experiences Porting Three Applications to OpenMP 4.5

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
6
2
1

Relationship

1
8

Authors

Journals

citations
Cited by 18 publications
(7 citation statements)
references
References 10 publications
0
7
0
Order By: Relevance
“…However, OpenMP faces more challenges than OpenACC for C++ code due to the lack of UVM support in the current compiler implementations [6,7].…”
Section: Openmp 45mentioning
confidence: 43%
“…However, OpenMP faces more challenges than OpenACC for C++ code due to the lack of UVM support in the current compiler implementations [6,7].…”
Section: Openmp 45mentioning
confidence: 43%
“…Starting with version 4.0, OpenMP is capable of offloading computations to GPUs thus raising performance challenges for both on-device computation and host-device communication. Some of the early experiences with OpenMP are outlined by Karlin et al [8] and Vergara Larrea et al [9]. For some time, the OpenMP standard has required explicit handling of data between host and device using maps.…”
Section: Related Workmentioning
confidence: 99%
“…An annual hackathon event for the improvement of OpenMP is hosted by IBM, where a live porting exercise is performed involving multiple US labs [11]. As an outcome of the 2015 hackathon, Karlin et al [12] ported the applications Kripke, Cardioid, and LULESH to OpenMP, demonstrating some issues with the interoperability with some features of C++, and achieving performance with LULESH within 10% of an equivalent CUDA port.…”
Section: Related Workmentioning
confidence: 99%