-
Notifications
You must be signed in to change notification settings - Fork 108
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
Call parameter type does not match function signature #999
Comments
Looking at this. |
So, I just tried to reproduce this error, building rocRAND, with latest HCC and HIP, and I couldn't reproduce the error you're seeing. But I'm not terribly surprised that you ran into this problem. There are a lot of "moving parts" (HCC, HIP, and rocRAND) and it is easy to run into this situation, especially if you're building some, or all, of these from source. I would recommend, if you're primarily interested in only rocRAND, to use the already built HCC/HIP binaries from the Debian repo. And if you build rocRAND from source, to consider two things: 1) use a docker container to help minimize any "contamination" on your machine, and 2) when you do build, and then rebuild rocRAND, completely remove the "build" directory - don't trust make clean to do a good enough job of cleaning. If you want to build HCC and/or HIP from source too, consider the above recommendations as well (use a docker container, and always completely remove build directory). And build/install HCC completely first, then HIP, then rocRAND. Let me know if you are still running into this issue. Cheers |
Hi, I'm using ArchLinux and have rebuilt everything from scratch (roct-thunk-interface -> rocr-runtime -> hcc -> hip -> rocrand), still getting the same error when building rocrand:
I've built the master branch of all components. Can you please provide the exact revision of these components you have used @david-salinas ? I prefer building everything from scratch, so I can properly package these components for ArchLinux. Thanks, |
Same error for me. @david-salinas I hate Docker, but of course I'm building in a clean chroot. |
I've checked the latest HCC (
rocRAND can be built. However, there is a recent commit (1d05859, https://github.com/RadeonOpenCompute/hcc/commits/clang_tot_upgrade) that updates submodules. |
@ex-rzr Hi, With the same config like you (release builds of hcc |
Turned out that Even if there is an incorrect code in rocRAND (but I don't see it), the compiler must show an error, not crush. What do you think? |
@david-salinas, do you have a build of the compiler that does not crash on this, so we can see the error? In the short term, how can we override |
See ROCm/rocRAND#40
rocRAND cannot be built using HCC > 1.3.18482.
It looks like a compiler bug, but if it's not, any ideas how to fix this are welcome.
(We can't understand what commit should be used to build 1.3.18482, i.e. the version of HCC in official debs).
The text was updated successfully, but these errors were encountered: