You'll need to add this year to all.py
On Oct 25, 2015 07:08, "Gregory Hainaut" wrote:
> Related to mesa issue: https://bugs.freedesktop.org/show_bug.cgi?id=79783
>
> Mostly "Validated" on Nvidia driver. Nvidia fails to link
> vs_fs_prog_separate_inactive
>
> v2:
> *
Same with this one
On Oct 25, 2015 07:08, "Gregory Hainaut" wrote:
> Test is composed of 2 major steps.
>
> First part ensure that a matching (same on both VS & FS) qualifier doesn't
> pertubate the location assignment
>
> Second part ensure that a non-matching
Related to mesa issue: https://bugs.freedesktop.org/show_bug.cgi?id=79783
Mostly "Validated" on Nvidia driver. Nvidia fails to link
vs_fs_prog_separate_inactive on first test
v3:
* Add a new test to ensure matching with various qualifier
To be discussed. I don't know, if behavior is
Related to mesa issue: https://bugs.freedesktop.org/show_bug.cgi?id=79783
Mostly "Validated" on Nvidia driver. Nvidia fails to link
vs_fs_prog_separate_inactive
v2:
* Test both output and input are still active
* Test real interstage variable are still optimized
* Mix rendezvous by name and
From: Emil Velikov
As per the spec the block must be of std140 (or std430 if using ssbo)
layout.
Signed-off-by: Emil Velikov
---
.../compiler/explicit-offsets/packed-layout.vert | 25 ++
From: Emil Velikov
Check if one member is (attempted to be) positioned on top of another,
and that the assigned offset(s) increase naturally.
Signed-off-by: Emil Velikov
---
.../explicit-offsets/decreasing-offset.vert| 27
Hi all,
Here are some tests on the said topic. These should cover the section
minus two bits;
1. "The *offset* qualifier can only be used on block members of blocks
declared with *std140* or *std430* layouts.
Afaict here one will need to use two separate shaders, as otherwise
providing
From: Emil Velikov
Check if both numberical and const expressions are accepted as valid
offset. Also try a negative value as offset.
Signed-off-by: Emil Velikov
---
.../integral-constant-expression-offset.vert | 28