On Mon, Apr 3, 2017 at 1:37 PM, Mark Janes wrote:
>
> This commit appears to intermittently provoke gpu hangs on 32-bit Intel
> systems when running
>
> piglit.shaders.glsl-max-varyings >max_varying_components
>
> Since the behavior is intermittent, I may have identified
This commit appears to intermittently provoke gpu hangs on 32-bit Intel
systems when running
piglit.shaders.glsl-max-varyings >max_varying_components
Since the behavior is intermittent, I may have identified the wrong
patch. Please let me know if this patch seems unlikely to affect the
test.
On Thu, Mar 30, 2017 at 3:47 PM, Matt Turner wrote:
> On Thu, Mar 30, 2017 at 3:26 PM, Grazvydas Ignotas
wrote:
>> There are still some distributions trying to support unfortunate people
>> with old or exotic CPUs that don't have 64bit atomic operations.
On Thu, Mar 30, 2017 at 3:26 PM, Grazvydas Ignotas wrote:
> There are still some distributions trying to support unfortunate people
> with old or exotic CPUs that don't have 64bit atomic operations. When
> compiling for such a machine, gcc conveniently inserts a library call to
There are still some distributions trying to support unfortunate people
with old or exotic CPUs that don't have 64bit atomic operations. When
compiling for such a machine, gcc conveniently inserts a library call to
a helper, but it's implementation is missing and we get a linker error.
This allows