-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use hcc_hsail in Rocm 1.3 #170
Comments
could you try add "--amdgpu-target=AMD:AMDGPU:8:0:1" in your compile option? The default compiler backend now generates GCN instructions instead of HSAIL by default, and |
Thank you for the reply. I had added the '--amdgpu-target=AMD:AMDGPU:8:0:1' in my compile option. But when I run the program, it still crash and return error information as follows: HCC STATUS_CHECK Error: HSA_STATUS_ERROR_INCOMPATIBLE_ARGUMENTS (0x100d) at file:/home/scchan/code/github/radeonopencompute/hcc.1.3/hcc/lib/hsa/mcwamp_hsa.cpp line:2504Aborted (core dumped) Follows is my compile command(in ROCM 1.3) ,it doesn't work: Before I update ROCM to 1.3. My compile command as follows and it works well: What should I do to fix it? Thanks. From: Wen-Heng (Jack) Chung |
I add '--amdgpu-target=AMD:AMDGPU:7:0:0' instead of '--amdgpu-target=AMD:AMDGPU:8:0:1. Thanks again! |
I had compiled my code successful and run correctly in rocm 1.2 envrionment(Kaveri).
But after I update the rocm to 1.3, I found it seems the hcc_hsail had been deprecated.
So, I use '/opt/rocm/hcc/' instead of
/opt/rocm/hcc-hsail/
. (for instance , use /opt/rocm/hcc/bin/hcc/opt/rocm/hcc/bin/hcc-config --cxxflags --ldflags
-I /opt/rocm/hcc/include/ xxx.cpp -o xxx to compile). It compiles successful.But it returns error when running.follows is the error information.
HCC STATUS_CHECK Error: HSA_STATUS_ERROR_INCOMPATIBLE_ARGUMENTS (0x100d) at file:/home/scchan/code/github/radeonopencompute/hcc.1.3/hcc/lib/hsa/mcwamp_hsa.cpp line:2504
Abortado (`core' generado)
How can I compile my code in Kaveri envrionment with rocm 1.3?
The text was updated successfully, but these errors were encountered: