On Monday, September 23, 2013 10:28:17 PM Marek Olšák wrote:
Is there another, more readable way to emulate the ?: operator from C?
I don't like adding unnecessary lines of code.
Marek
On Mon, Sep 23, 2013 at 10:23 PM, Dylan Baker baker.dyla...@gmail.com
wrote:
On Saturday, September
From: Marek Olšák marek.ol...@amd.com
---
piglit-run.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/piglit-run.py b/piglit-run.py
index 7e99791..889d7e2 100755
--- a/piglit-run.py
+++ b/piglit-run.py
@@ -62,7 +62,7 @@ def main():
action = append,
On Monday, September 23, 2013 11:12:50 PM mar...@gmail.com wrote:
From: Marek Olšák marek.ol...@amd.com
---
piglit-run.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/piglit-run.py b/piglit-run.py
index 7e99791..889d7e2 100755
--- a/piglit-run.py
+++
---
.../built-in-functions/fs-uaddCarry.shader_test| 55 ++
1 file changed, 55 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-uaddCarry.shader_test
diff --git
---
.../fs-uaddCarry-only-add.shader_test | 52 ++
1 file changed, 52 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-uaddCarry-only-add.shader_test
diff --git
---
.../fs-uaddCarry-only-carry.shader_test| 52 ++
1 file changed, 52 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-uaddCarry-only-carry.shader_test
diff --git
---
.../built-in-functions/fs-usubBorrow.shader_test | 48 ++
1 file changed, 48 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-usubBorrow.shader_test
diff --git
---
.../fs-usubBorrow-only-borrow.shader_test | 46 ++
1 file changed, 46 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-usubBorrow-only-borrow.shader_test
diff --git
---
.../fs-usubBorrow-only-sub.shader_test | 46 ++
1 file changed, 46 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-usubBorrow-only-sub.shader_test
diff --git
---
.../built-in-functions/vs-uaddCarry.shader_test| 65 ++
1 file changed, 65 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-uaddCarry.shader_test
diff --git
---
.../vs-uaddCarry-only-carry.shader_test| 62 ++
1 file changed, 62 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-uaddCarry-only-carry.shader_test
diff --git
---
.../vs-uaddCarry-only-add.shader_test | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-uaddCarry-only-add.shader_test
diff --git
---
.../built-in-functions/vs-usubBorrow.shader_test | 58 ++
1 file changed, 58 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-usubBorrow.shader_test
diff --git
---
.../vs-usubBorrow-only-sub.shader_test | 56 ++
1 file changed, 56 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-usubBorrow-only-sub.shader_test
diff --git
---
.../vs-usubBorrow-only-borrow.shader_test | 56 ++
1 file changed, 56 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-usubBorrow-only-borrow.shader_test
diff --git
The multisampling tests initialize the number of miplevels to the number
of samples. Since this is zero, we allocate an array of zero miplevels,
and then try to write to the first element.
Fixes the following Valgrind error:
Invalid write of size 8
at 0x403123: compute_miplevel_info
16 matches
Mail list logo