[Pkg-opencl-devel] Bug#769293: beignet: upgrade or OCL_STRICT_CONFORMANCE change requires reboot

[Zhigang Gong]

Actually OCL_STRICT_CONFORMANCE is just an environment variable. Each
time you change this
variable, it will take effect next time you run the opencl application
if the application will build the kernel again.

For example the opencv 3.0 test case will build kernel each time, so
we can easily set to non strict mode
then run some cases with non-strict math functions. Then latter, after
those cases finished, we can set
it to strict mode, then run the same cases under strict math mode. It
works. And we use ICD as well.

If the application will cache the built kernel binary, then the second
time setting the strict mode will not
take effect unless you delete the previous binary files. OpenCV 2.4
test cases are using this style.

Don't quite understand this issue. How do you set the OCL_STRICT_CONFORMANCE?

On Wed, Nov 12, 2014 at 10:26 PM, Rebecca N. Palmer
<rebecca_palmer at zoho.com> wrote:
> Package: beignet
> Version: 0.9.3~dfsg-1
>
> When beignet is used as an ICD (which is the recommended way to use an
> OpenCL library), only the first run after a reboot can change the
> OCL_STRICT_CONFORMANCE (accuracy vs. speed) setting, or load a
> newly-installed beignet version.  Running ldconfig or using a new terminal
> window doesn't help.
>