Le 19/05/2020 à 14:26, Mo Zhou a écrit :
But I am more than open for help with the llvm-roc build, since this not
even finishes on my computer without blowing it up ATM ...
My experience is that LLVM build often ends up being killed by the OOM
killer, and I can only use -j4 on a machine with
On Tue, May 19, 2020 at 08:41:47PM +0900, Norbert Preining wrote:
> > Packaging ROCm requires a forked LLVM. Will you package that fork, and
>
> Thanks for bringing this up. Up to now all the ITP don't require the
> forked llvm. We have one repository (rocm-hip) in preparation for which
> the llv
Hi doko,
I've not dug into this deep enough by myself. AFAIK, however, AMD seemd
to have upstreamed their LLVM bits specific to LLVM
https://github.com/RadeonOpenCompute/hcc/issues/1421
https://github.com/RadeonOpenCompute/hcc#deprecation-notice
I asked the corresponding Gentoo developer and he co
Hi Matthias,
> Packaging ROCm requires a forked LLVM. Will you package that fork, and
Thanks for bringing this up. Up to now all the ITP don't require the
forked llvm. We have one repository (rocm-hip) in preparation for which
the llvm-fork is necessary. And there are other's I am preparing.
Ou
On 5/19/20 3:29 AM, Norbert Preining wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Norbert Preining
>
> * Package name: rocr-runtime
> Version : 3.3.0
> Upstream Author : AMD
> * URL : https://github.com/RadeonOpenCompute/ROCR-Runtime/
> * License : Univ
Package: wnpp
Severity: wishlist
Owner: Norbert Preining
* Package name: rocr-runtime
Version : 3.3.0
Upstream Author : AMD
* URL : https://github.com/RadeonOpenCompute/ROCR-Runtime/
* License : University of Illinois/NCSA Open Source License
Programming Lang
6 matches
Mail list logo
