Re: [Beignet] Weird clinfo ouput @ FreeBSD-11.0/Intel GPU

That looks like abi::__cxa_demangle is sometimes failing completely (and possibly inconsistently, given that it's failing on a different symbol this time). Given that it only happens on FreeBSD, possibly a libc++ (LLVM) vs libstdc++ (GCC) issue?? ___

Re: [Beignet] Weird clinfo ouput @ FreeBSD-11.0/Intel GPU

> possibly a name demangling problem? > To find out, try this The result is: platform number 1 platform_profile "FULL_PROFILE" platform_name "Intel Gen OCL Driver" platform_vendor "Intel" platform_version "OpenCL 1.2 beignet 1.2" platform_extensions "cl_khr_global_int32_base_atomics

[Beignet] [PATCH V2 3/3] Backend: Add hole reuse in reg alloction

From: Pan Xiuli We first find regs that have pool in simple linear scale, and save them in HoleRegPool, when allocte regs we first try to search fit candidate in the pool and choose the most fit one to reuse. V2: Refine hole reuse only in one block. DEBUG version: You can

Re: [Beignet] Weird clinfo ouput @ FreeBSD-11.0/Intel GPU

> builtin_kernel_block_motion_estimate_intel()[SUCCESS] > runtime_climage_from_boname()Unresolved symbol: > _Z22__gen_ocl_write_imagef11ocl_image2dDv2_iDv4_f > Aborting... That message is from backend/src/llvm/llvm_gen_backend.hpp:97, and means it can't find that function (in its internal