From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 70891] New: CL_INVALID_BUILD_OPTIONS results in
CL_INVALID_DEVICE when asking for build log
Date: Sat, 26 Oct 2013 12:18:29 +0000
Message-ID:
Priority
medium
Bug ID
70891
Assignee
dri-devel@lists.freedesktop.org
Summary
CL_INVALID_BUILD_OPTIONS results in CL_INVALID_DEVICE when asking for build log
Severity
normal
Classification
Unclassified
OS
Linux (All)
Reporter
brunojimen@gmail.com
Hardware
x86-64 (AMD64)
Status
NEW
Version
git
Component
Drivers/Gallium/r600
Product
Mesa
When you use an invalid option to build a program, you get the
CL_INVALID_BUILD_OPTIONS error, but somehow it also makes the device used for
the build invalid. So if you after that asks for the build log with
clGetProgramBuildInfo you get also a CL_INVALID_DEVICE.
Way to reproduce this bug:
1- Clone tstellard's repo of opencl-examples:
http://cgit.freedesktop.org/~tstellar/opencl-example/
2- Modify hello-world.c at line 112 to some invalid options.
3- Compile and run it, it fails at the clGetPrograBuildInfo some lines below.
Expected output:
Maybe an empty log and a CL_INVALID_BUILD_OPTIONS error.
This bug may make difficult to track problems because one may think that the
device is wrong, when all that has happened is that he have used wrong build
options.