Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-10-18 Thread Diederik de Haas
On Sat, 17 Oct 2020 14:23:29 +0600 Sajjad Kabir Joy  
wrote:
> so I think it had been an LLVM issue all along)

That's is/was my suspicion too.
You can close this bug by sending a mail to -done@b.d.o

signature.asc
Description: This is a digitally signed message part.


Bug#964791: [Pkg-opencl-devel] Bug#964791: Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-10-17 Thread Diederik de Haas
On vrijdag 16 oktober 2020 23:12:31 CEST Rebecca N. Palmer wrote:
> whether mesa-opencl-icd actually works.  Have you checked this?

No, but I haven't done anything with OpenCL ever.
I assumed that if 'clinfo' doesn't work, nothing works wrt OpenCL.


signature.asc
Description: This is a digitally signed message part.


Bug#964791: [Pkg-opencl-devel] Bug#964791: Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-10-17 Thread Sajjad Kabir Joy
I switched over to AMDGPU-Pro OpenCL driver, and just now tested that with
LLVM 11, mesa-opencl-icd does work (I had previously tested Mesa 20.2 with
LLVM 10, which didn't work, so I think it had been an LLVM issue all along).


Bug#964791: [Pkg-opencl-devel] Bug#964791: Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-10-16 Thread Rebecca N. Palmer
The error message has gone for me as well, but I don't have the hardware 
to tell whether mesa-opencl-icd actually works.  Have you checked this?


I agree that this is probably the same bug as #964973, which is marked 
as fixed.




Bug#964791: [Pkg-opencl-devel] Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-10-16 Thread Diederik de Haas
Does this error still occur?

It seems to me the same problem as in https://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=964973 and that has been fixed for me.
With me, 'clinfo' didn't work before, but it does now.

signature.asc
Description: This is a digitally signed message part.


Bug#964791: [Pkg-opencl-devel] Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-07-10 Thread Rebecca N. Palmer
This error occurs when clinfo is run with mesa-opencl-icd installed; it 
does _not_ require actual AMD hardware.


Previous similar bugs suggest that compiling libclc/mesa-opencl-icd with 
-Bsymbolic, and/or statically linking them to LLVM/Clang, might help:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768185
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852746

However, unlike those bugs, this one occurs even if mesa-opencl-icd is 
the only ICD installed.




Bug#964791: libclc-amdgcn: OpenCL fails to start

2020-07-10 Thread Sajjad Kabir Joy
Package: libclc-amdgcn
Version: 0.2.0+git20190827-6
Severity: important
Tags: upstream
X-Debbugs-Cc: sajjadkabir...@gmail.com

Dear Maintainer,


OpenCL fails to initiate (and any program using it). For example, clinfo shows 
this:

: CommandLine Error: Option 'polly' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

I am using AMD Kaveri APU (R7 graphics) with AMDGPU.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libclc-amdgcn depends on:
ii  libclang-common-10-dev  1:10.0.1~+rc4-1
ii  libclc-dev  0.2.0+git20190827-6

libclc-amdgcn recommends no packages.

libclc-amdgcn suggests no packages.

-- no debconf information