On Fri, Jan 26, 2018 at 05:59:37PM -0800, Jason Ekstrand wrote:
> ---
> src/compiler/nir/nir_format_convert.h | 26 ++
> 1 file changed, 26 insertions(+)
I don't what is the official reference for the formulas and I just took what
google gave me first. There was discussion
On Fri, Jan 26, 2018 at 05:59:36PM -0800, Jason Ekstrand wrote:
> ---
> src/compiler/Makefile.sources | 1 +
> src/compiler/nir/meson.build | 1 +
> src/compiler/nir/nir_format_convert.h | 106
> ++
> 3 files changed, 108 insertions(+)
> creat
Hi
Sorry to be a pain again
I've just tested this with clang and the 32bit build still fails without
-latomic
libtool: link: /bin/true glsl/.libs/libstandalone.a
libtool: link: rm -fr glsl/.libs/libstandalone.lax
glsl/.libs/libstandalone.lax
libtool: link: ( cd "glsl/.libs" && rm -f "libstandalo
Neither GL nor CL nor SPIRV needs the IEEE handling of sNaNs.
Signed-off-by: Jan Vesely
---
This is the 3rd way to handle broken fmin/fmax in clover CL.
It can be worked around in libclc (to not use
llvm.fminnum/llvm.fmaxnum)[0]
LLVM can be patched to not use IEEE_MODE[1]
Or it can be fixed in th
On Thu, Mar 01, 2018 at 03:04:14PM -0800, Jason Ekstrand wrote:
> On Thu, Mar 1, 2018 at 6:49 AM, Pohjolainen, Topi <
> topi.pohjolai...@gmail.com> wrote:
>
> > On Mon, Feb 26, 2018 at 08:42:42AM -0800, Jason Ekstrand wrote:
> > > On Mon, Feb 26, 2018 at 6:19 AM, Pohjolainen, Topi <
> > > topi.poh
On Fri, Mar 2, 2018 at 1:38 PM, Emil Velikov wrote:
> Hi Alex,
>
> On 28 February 2018 at 15:25, Alex Smith wrote:
>> Hi,
>>
>> Could this (commit 5d61fa4e68b7eb6d481a37efdbb35fdce675a6ad on master) be
>> backported to the 17.3 branch to allow it to build with LLVM 6?
>>
> Normally we don't aim t
On Fri, Mar 2, 2018 at 7:55 PM, Daniel Díaz Rodríguez
wrote:
> Hello, Rob!
>
>
> On 14 July 2017 at 10:29, Daniel Díaz wrote:
>> Those functions are not available on libMali, thus breaking
>> builds and creating havoc.
>>
>> Removing the specific parts of the code that deal with
>> gbm_bo_map() a
Patch by "Tomas Chvatal" with modifications
by "Michal Srb" to not break python 2.
https://bugzilla.suse.com/show_bug.cgi?id=1082303
v2:
- no longer try to encode a unicode
- make use of 'from __future__ import print_function', so semantics
of print statements in python2 are closer to print f