Package: piglit Version: 0~git20150829-59d7066-1.1 Severity: important Tags: upstream
Hi, this is a bit of a showstopper here: the CL tests do not actually verify that the size of the data returned matches the expectation, but rather they just cast a pointer to the result buffer to a pointer to the expected type, dereference it and interpret the result. This is fairly wrong, and fails in an unsubtle way for the CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE test: This item is a cl_ulong, i.e. always 64 bits. The test always interprets the result as a signed(!) int(!), which is 32 bits. Changing this to size_t does not help, because that is still 32 bit wide on 32 bit architectures. It finally falls over completely on big endian architectures, where now the upper 32 bits of a 64 bit value are tested, and as our constant buffer is smaller than 256 Terabytes, the test then fails. This is a systemic problem, however. None of the info values are tested for data type. Simon -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages piglit depends on: ii libc6 2.24-7 ii libdrm-intel1 2.4.74-1 ii libdrm2 2.4.74-1 ii libegl1-mesa [libegl1-x11] 13.0.2-1 ii libgcc1 1:6.2.1-5 ii libgl1-mesa-glx [libgl1] 13.0.2-1 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libstdc++6 6.2.1-5 ii libwaffle-1-0 1.5.2-2 ii libx11-6 2:1.6.3-1 ii libxcb-dri2-0 1.12-1 ii ocl-icd-libopencl1 [libopencl1] 2.2.9-2 ii python-mako 1.0.4+ds1-2 ii python-six 1.10.0-3 pn python:any <none> piglit recommends no packages. piglit suggests no packages. -- no debconf information
