2013
DOI: 10.1016/j.parco.2013.09.003
|View full text |Cite
|
Sign up to set email alerts
|

Characterizing the challenges and evaluating the efficacy of a CUDA-to-OpenCL translator

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 8 publications
(6 citation statements)
references
References 13 publications
0
6
0
Order By: Relevance
“…CU2CL Gardner et al summarize the challenges of translating CUDA code to its OpenCL equivalence (Gardner et al 2013). They develop an automated CUDA-to-OpenCL source-to-source translator (CU2CL), to automatically translate three medium-to-large, CUDA-optimized codes to OpenCL, thus enabling the codes to run on other GPU-accelerated systems (Martinez et al 2011;Sathre et al 2019).…”
Section: Cuda-to-openclmentioning
confidence: 99%
“…CU2CL Gardner et al summarize the challenges of translating CUDA code to its OpenCL equivalence (Gardner et al 2013). They develop an automated CUDA-to-OpenCL source-to-source translator (CU2CL), to automatically translate three medium-to-large, CUDA-optimized codes to OpenCL, thus enabling the codes to run on other GPU-accelerated systems (Martinez et al 2011;Sathre et al 2019).…”
Section: Cuda-to-openclmentioning
confidence: 99%
“…A most intuitive way of the code translation is to let programmers manually translate the code of each platform by substituting similar API functions. There are also many efforts to achieve automatic translations, as shown in [22][23][24]. Researches show that the automatically translated code also performs well, at least for the case of converting CUDA codes to OpenCL codes.…”
Section: Translations Between Cuda and Openclmentioning
confidence: 99%
“…The CU2CL tool [12] is an automated CUDA-to-OpenCL source-tosource translator (CU2CL), enabling portability of CUDA software to platforms lacking a CUDA implementation. We chose OpenCL as the target language for the following reasons: (1) its broad-based adoption and support, e.g., it currently supports not only GPUs but also CPUs, Intel Xeon Phi, and even FPGAs, (2) a similar programming model to CUDA, and (3) a "write-once, run-anywhere" open standard.…”
Section: Cu2cl Translatormentioning
confidence: 99%
“…• A unified runtime layer implemented on top of CUDA and one or more other models that support other devices • Automatic source-level translation of kernel and/or host code • Automatic conversion of PTX IR to another device's IR • Runtime compatibility or wrapper layers between CUDA and one or more other models Here we leveraged CU2CL [12], a compiler-based CUDA-to-OpenCL auto-translator for both kernel and host code, that uses a small amount of on-the-fly generated runtime compatability code to construct functionally-equivalent analogs to CUDA functions. Closely related is the work of Kim et al [16], which provides hand-written bi-directional runtime wrapper layers between CUDA and OpenCL host code and a kernel translator; this work is distinguished from CU2CL by providing an OpenCL-to-CUDA compatibility layer but not aiming to provide a static translation of the host runtime API and providing a compatibility layer instead.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation