public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marek Szuba <marecki@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Package up for grabs: dev-libs/amdgpu-pro-opencl
Date: Mon, 30 Sep 2019 13:53:39 +0100	[thread overview]
Message-ID: <ea1206c3-2ad7-c2df-8efe-2e86e3bc230b@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1347 bytes --]


For those of you not familiar with it, dev-libs/amdgpu-pro-opencl
packages the OpenCL bits of the proprietary, binary-only AMDGPU-Pro
software stack into a form compatible with the Open Source amdgpu
environment in general and Gentoo in particular. It has been working
surprisingly well for an ugly hack it is but now that we have Radeon
Open Compute-based OpenCL support for amdgpu (which will eventually be
fully Open Source and at the moment only requires proprietary libraries
for one last feature, image support) in the tree I feel it is time for
it to go - especially given that it only support AMD GPUs older than
Vega 10.

Unfortunately it would be awkward to simply last-rite because the
ROC-based implementation does not support ABI_X86_32
(dev-libs/rocm-opencl-runtime and its dependencies may or may not work
in 32-bit mode but have neither multilib support nor x86 keywords at
present, whereas the closed-source components are only available for
native amd64).

No open tickets on Bugzilla, binaries for both versions currently in the
tree are still available, and beyond the obvious shortcoming of not
supporting more recent GPUs in spite of upstream providing appropriate
libraries (I haven't tried packaging them because my AMD GPU is too old
to test them on), no real problems at the moment.

-- 
MS


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2019-09-30 12:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea1206c3-2ad7-c2df-8efe-2e86e3bc230b@gentoo.org \
    --to=marecki@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox