Szilárd Páll

OK, looking forward to seeing the 1.9 not crash, but admittedly I'd be more relieved if somebody confirmed that the release branch is in fact fixed. (Unrelated, but I'm hoping...

> OK, looking forward to seeing the 1.9 not crash, but admittedly I'd be more relieved if somebody confirmed that the release branch is in fact fixed. Though if 1.9...

After updating the toolchain to ROCm 1.9, I am still getting a clBuildProgram() segfault, so unfortunately this seems to have fallen through the cracks. How long until the next patch...

Thanks for the feedback @b-sumner and @jlgreathouse. I appreciate that the planning for 1.9.x is ongoing. Is there a (reasonably straightforward!) way for me to build and replace the rocm-opencl...

> One possibility might be to reduce each component separately instead of all 3 at once. Thanks for the tip. Unfortunately it did not work. Strange thing is that if...

It seems like this missed the 1.9.1 too, right? Any plans to release a new rocm-opencl?

That's very unfortunate. Is there an approx ETA for ROCm 2.0 (I know it has just been announced, but announcement != release and we need to advise out users whether...

@jlgreathouse OK, I understand that the cost of backporting a fix is too high to address this issue. End of the year would be great, I hope I can get...

We are getting close to our final release and at the moment 1.9 is still not working. I've seen some links to 2.0 beta rpms floating around on the Internet,...

Not sure if related, but in the meantime I see the following messages in dmesg: ``` [209359.980927] perf: interrupt took too long (2510 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [258359.848121]...