Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jul 2017 10:56:44 -0500
From:      Steven Nikkel <>
To:        Jan Beich <>
Subject:   Re: OpenCL Issues
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2017-07-17 1:53 AM, Jan Beich wrote:
> Steven Nikkel <> writes:
>> On 2017-07-14 6:11 PM, Jan Beich wrote:
>>> Steven Nikkel <> writes:
>>>> On 2017-07-14 8:13 AM, Jan Beich wrote:
>>>>> See
>>>> Thanks, work around from the bug report solves my issue with beignet
>>>> and I can successfully use OpenCL on that host.
>>>               ^^^^^^^^^^^
>>> Awesome! I'd like to update the port to a snapshot to pick up the fix in
>>> question upstream, LLVM 4.0 support, more optimizations and catch
>>> regressions early. Can you give it a try?
>>> (see Download Raw Diff)
>> The update builds and installs. It runs clinfo fine, but I'm getting
>> errors in my CL app, looks like it can't find the cl_amd_media_ops
>> extension. Not sure where that error comes from as it's fine in the
>> 1.3.1 from the existing port.
> What does clinfo show? Is cl_amd_media_ops listed in among extensions?
> Can you try building against LLVM 3.9 (MESA_LLVM_VER=39) or LLVM 5.0
> (MESA_LLVM_VER=-devel) via lang/beignet/Makefile.local? Can you post
> a link to the source, assuming it's an open project?
> I can't reproduce and not familar enough with OpenCL to guess. Maybe bisect.

The cl_amd_media_ops extension isn't listed in clinfo for the working or 
non working beignet case.

This is the specific source generating that error:

The overall source isn't currently setup to build in FreeBSD, that is 
what I'm working on.

I noticed it's wrapped in a test to check for the extension before using 
it. Not sure if that is the correct way or not.

Tried building patched beignet with LLVM 3.9, different error message, 
fails an internal consistency check in the code.

Want to link to this message? Use this URL: <>