David Galiffi
5802abfbe6
Fix links in glossary.md and faqs.md which still refer to the archived organizations.
Change-Id: I1d2841be100bf129485684af06d2e7f0f8bc40f6
[ROCm/hip commit: d62ffdd9c5]
24 righe
1.4 KiB
Markdown
24 righe
1.4 KiB
Markdown
# Terms used in HIP Documentation
|
|
|
|
- host, host cpu : Executes the HIP runtime API and is capable of initiating kernel launches to one or more devices.
|
|
- default device : Each host thread maintains a "default device".
|
|
Most HIP runtime APIs (including memory allocation, copy commands, kernel launches) do not use accept an explicit device
|
|
argument but instead implicitly use the default device.
|
|
The default device can be set with hipSetDevice.
|
|
|
|
- "active host thread" - the thread which is running the HIP APIs.
|
|
|
|
- HIP-Clang - Heterogeneous AMDGPU Compiler, with its capability to compile HIP programs on AMD platform (https://github.com/ROCm/llvm-project).
|
|
|
|
- clr - a repository for AMD Common Language Runtime, contains source codes for AMD's compute languages runtimes: HIP and OpenCL™.
|
|
clr (https://github.com/ROCm/clr) contains the following three parts,
|
|
hipamd: contains implementation of HIP language on AMD platform.
|
|
rocclr: contains common runtime used in HIP and OpenCL™, which provides virtual device interfaces that compute runtimes interact with different backends such as ROCr on Linux or PAL on Windows.
|
|
opencl: contains implementation of OpenCL™ on AMD platform.
|
|
|
|
- hipify tools - tools to convert CUDA code to portable C++ code (https://github.com/ROCm/HIPIFY).
|
|
|
|
- hipconfig - tool to report various configuration properties of the target platform.
|
|
|
|
- nvcc = nvcc compiler, do not capitalize.
|