Martin Schleiss
263dcfed83
Conflicts: README.md Change-Id: Ie296d503d16121a62fed1a208352ec2b81c97fd9
20 라인
915 B
Markdown
20 라인
915 B
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.
|
|
|
|
- completion_future becomes ready. "Completes"
|
|
|
|
- hcc = Heterogeneous Compute Compiler (https://bitbucket.org/multicoreware/hcc/wiki/Home).
|
|
|
|
- hipify - tool to convert CUDA(R) code to portable C++ code.
|
|
- hipconfig - tool to report various configuration properties of the target platform.
|
|
|
|
- nvcc = nvcc compiler, do not capitalize.
|
|
- hcc = heterogeneous compute compiler, do not capitalize.
|