ROCm-OpenCL-Runtime
ROCm
Our great sponsors
ROCm-OpenCL-Runtime | ROCm | |
---|---|---|
15 | 198 | |
171 | 3,637 | |
- | - | |
0.0 | 0.0 | |
3 months ago | 4 months ago | |
C++ | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ROCm-OpenCL-Runtime
-
ROCm Is AMD's #1 Priority, Executive Says
Its not that they're supporting buggy code, they just downgraded the quality of their implementation significantly. They made the compiler a lot worse when they swapped to rocm
https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime/iss... is the tracking issue for it filed a year ago, which appears to be wontfix largely because its a lot of work
OpenCL still unfortunately supports quite a few things that vulkan doesn't, which makes swapping away very difficult for some use cases
-
rocm-opencl (rocm-opencl-runtime) rx 6600 xt support
There's https://docs.amd.com/bundle/ROCm-Installation_FAQ/page/Frequently_Asked_Questions.html which leads to a page which doesn't list any gpus that I can see, there's https://rocm.docs.amd.com/en/latest/release/gpu_os_support.html which lists "RDNA2" , there's https://github.com/RadeonOpenCompute/ROCm/issues/1698 which is from last year and mentions changing an env for the RX 6600 XT (navi 23) . Not a lot is mentioned in the readme of https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime .
-
Install ROCm Fedora 38
$ dnf info rocm-opencl Installed Packages Name : rocm-opencl Version : 5.4.3 Release : 2.fc38 Architecture : x86_64 Size : 1.7 M Source : rocm-opencl-5.4.3-2.fc38.src.rpm Repository : @System From repo : updates Summary : ROCm OpenCL Runtime URL : https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime License : MIT Description : ROCm OpenCL language runtime. : Supports offline and in-process/in-memory compilation.
-
Horrible Code, Clean Performance
Thank you for subscribing to AMD OpenCL Facts! To unsubscribe please type AARRHGHGH. I'm open for questions though, and the bug report for this is here. For more mildly disgruntled rambling:
-
First time in 2 years I was able to get Blender running with an AMD GPU on Linux!
Eg this bug about shared cl/gl textures with mipmaps being broken has now breached its first birthday, without even acknowledgement - basic cl/gl functionality here. This bug took a year for a fix to make its way into a public driver. And this fairly performance critical bug is just "wontfix", and also a significant downgrade from their old driver stack
- Final fantasy 7 remake Green artifacts after switching to amd proprietary drivers
-
So far I'm unconvinced a 34MB binary blob is more free than OpenZFS.
Its definitely workable if you're willing to put in the effort (except for things that are straight up broken in some cases, like device side enqueue), but there are some issues that require.. fairly major workarounds
-
New NVIDIA Open-Source Linux Kernel Graphics Driver Appears
Their implementation is here: https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime
-
C++ Show and Tell - April 2022
After a lot of moderately annoyed testing, I discovered that the AMD OpenCL implementation is.. rather dumb. If any two kernels share any arguments arguments, it inserts a command barrier between the two, hard-stalling the GPU. After filing a bug, it turns out this is wontfix as well, which is doubly bad. There's no set of flags in OpenCL that you can use to fix this either
-
[TPU] AMD ROCm 4.5 Drops "Polaris" Architecture Support
What's particularly bizarre, is that with one bug report I filed, they claim to have fixed it internally in april, but.. no public driver has ever been released with the fix. For 7 months? Which is just a bizarre software development process
ROCm
-
AMD May Get Across the CUDA Moat
Yep, did exactly that. IMO he threw a fit, even though AMD was working with him squashing bugs. https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
- ROCm 5.7.0 Release
-
ROCm Is AMD's #1 Priority, Executive Says
Ok, I wonder what's wrong. maybe it's this? https://stackoverflow.com/questions/4959621/error-1001-in-cl...
Nope. Anything about this on the arch wiki? Nope
This bug report[2] from 2021? Maybe I need to update my groups.
[2]: https://github.com/RadeonOpenCompute/ROCm/issues/1411
$ ls -la /dev/kfd
-
Simplifying GPU Application Development with HMM
HMM is, I believe, a Linux feature.
AMD added HMM support in ROCm 5.0 according to this: https://github.com/RadeonOpenCompute/ROCm/blob/develop/CHANG...
-
AMD Ryzen APU turned into a 16GB VRAM GPU and it can run Stable Diffusion
Woot AMD now supports APU? I sold my notebook as i hit a wall when trying rocm [1] Is there a list oft Wirkung apu's ?
[1] https://github.com/RadeonOpenCompute/ROCm/issues/1587
-
Nvidia's CUDA Monopoly
Last I heard he's abandoned working with AMD products.
https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
-
Nvidia H100 GPUs: Supply and Demand
They're talking about the meltdown he had on stream [1] (in front of the mentioned pirate flag), that ended with him saying he'd stop using AMD hardware [2]. He recanted this two weeks after talking with AMD [3].
Maybe he'll succeed, but this definitely doesn't scream stability to me. I'd be wary of investing money into his ventures (but then I'm not a VC, so what do I know).
[1] https://www.youtube.com/watch?v=Mr0rWJhv9jU
[2] https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
[3] https://twitter.com/realGeorgeHotz/status/166980346408248934...
-
Open or closed source Nvidia driver?
As for rocm support on consumer devices, AMD wont even clarify what devices are supported. https://github.com/RadeonOpenCompute/ROCm/pull/1738
-
Why Nvidia Keeps Winning: The Rise of an AI Giant
He flamed out, then is back after Lisa Su called him (lmao)
https://geohot.github.io/blog/jekyll/update/2023/05/24/the-t...
https://www.youtube.com/watch?v=Mr0rWJhv9jU
https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div...
On a personal level that youtube doesn't make him come off looking that good... like people are trying to get patches to him and generally soothe him/damage control and he's just being a bit of a manchild. And it sounds like that's the general course of events around a lot of his "efforts".
On the other hand he's not wrong either, having this private build inside AMD and not even validating official, supported configurations for the officially supported non-private builds they show to the world isn't a good look, and that's just the very start of the problems around ROCm. AMD's OpenCL runtime was never stable or good either and every experience I've heard with it was "we spent so much time fighting AMD-specific runtime bugs and specs jank that what we ended up with was essentially vendor-proprietary anyway".
On the other other hand, it sounds like AMD know this is a mess and has some big stability/maturity improvements in the pipeline. It seems clear from some of the smoke coming out of the building that they're cooking on more general ROCm support for RDNA cards, and generally working to patch the maturity and stability issues he's talking about. I hate the "wait for drivers/new software release bro it's gonna fix everything" that surrounds AMD products but in this case I'm at least hopeful they seem to understand the problem, even if it's completely absurdly late.
Some of what he was viewing as "the process happening in secret" was likely people doing rush patches on the latest build to accommodate him, and he comes off as berating them over it. Again, like, that stream just comes off as "mercurial manchild" not coding genius. And everyone knew the driver situation is bad, that's why there's notionally alpha for him to realize here in the first place. He's bumping into moneymakers, and getting mad about it.
-
Disable "SetTensor/CopyTensor" console logging.
I tried to train another model using InceptionResNetV2 and the same issues happens. Also, this happens even using the model.predict() method if using the GPU. Probably this is an issue related to the AMD Radeon RX 6700 XT or some mine misconfiguration. System Inormation: ArchLinux 6.1.32-1-lts - AMD Radeon RX 6700 XT - gfx1031 Opened issues: - https://github.com/RadeonOpenCompute/ROCm/issues/2250 - https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/issues/2125
What are some alternatives?
tensorflow-upstream - TensorFlow ROCm port
tensorflow-directml - Fork of TensorFlow accelerated by DirectML
seer - Seer - a gui frontend to gdb
Pytorch - Tensors and Dynamic neural networks in Python with strong GPU acceleration
rocm-arch - A collection of Arch Linux PKGBUILDS for the ROCm platform
GPU-Raytracer - GPU Raytracer from scratch in C++/CUDA
oneAPI.jl - Julia support for the oneAPI programming toolkit.
chrgfx - Converts to and from tile based graphics from retro video game hardware
SHARK - SHARK - High Performance Machine Learning Distribution
muzero-cpp - A C++ pytorch implementation of MuZero
llama.cpp - LLM inference in C/C++