Cycles HIP binaries disabled due to compiler bugs #104786
- Enable on Windows (#107098)
- Enable on Linux (#107662)
- Enable Radeon VII (gfx906) - Not expected to get fixed, so will remain disabled
There are known bugs in HIP compiler that are causing random build failures when making changes to the Cycles kernel. This is preventing developers from efficiently making improvements to Cycles.
Cycles AMD GPU rendering were disabled in Blender 3.6 alpha, so that ongoing work like Principled v2 is not blocked. Additionally light tree sampling is not available for HIP in Blender 3.5. We hope this can be resolved later on in the 3.6 release cycle.
Relevant FIXME's in LLVM amdgpu backend (in fact I suspect we hit the same ones back when we were using OpenCL).
Just an update from the AMD side, the fix for the above issue is in progress on the compiler side. Can't comment on ETA at this point.
any news from AMD?
Thanks in advance,
When there is news it will be posted here, for now there is no news yet.
Can we have the HIP button disabled in the Settings for the time being? Possibly with an informative message? It's definitely contributing to a little confusion and wasted time for the bug team (see my own bug report #106225 )
Disabling HIP devices in ui should be fine, @brecht do you agree? I don't think it needs an involved message. This is temporary and 3.6 is in alpha, so I don't think it needs an involved user message.
Binaries were re-enabled on Windows now. Linux is still waiting for a new ROCm release, and gfx906 is also disabled due to an issue to be solved still.
Radeon VII is not expected to be fixed, so closing this issue as resolved since all the other ones work.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?