[Mesa-dev] [Bug 78581] OpenCL: clBuildProgram prints error messages directly rather than storing them

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=78581

--- Comment #2 from Luke-Jr <luke-jr+freedesktopbugs at utopios.org> ---
(In reply to comment #1)
> I though this was working.  Can you provide and example of the output when a
> shader fails to compile.

With my current setup, what happens seems to be LLVM tries to format FROM
unallocated memory (which prevents me from using gdb, but "gets away with it"
at normal runtime), prints something along the lines of "1 error(s)",
CL_PROGRAM_BUILD_LOG yields a null string, and the end result after testing
cause my system to lock up. :(

Prior to my first lock up, a message about <stddef.h> not being found was also
printed (strace showed it checking /usr/include and /usr/include/clc, but not
the documented /usr/lib/clang/3.4.1/include which actually has a stddef.h).

A few weeks ago, it worked on my 5850, but not 7xxx, which printed (directly)
compile errors. I *think* the main change since then was a LLVM upgrade.
Although I had to mess around quite a bit to get Open*G*L working again (which
turned out to be its SSSE3 memcpy replacement crashing on Haswell).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140512/32533975/attachment.html>