On Mon, Dec 7, 2015 at 5:18 PM, Kenneth Graunke wrote:
> On Monday, December 07, 2015 04:52:21 PM Jason Ekstrand wrote:
>> Previously, the VS_OPCODE_PULL_CONSTANT_LOAD opcode operated on
>> vec4-aligned byte offsets on Iron Lake and below and worked in terms of
>> vec4 offsets on Sandy Bridge. On
On Monday, December 07, 2015 04:52:21 PM Jason Ekstrand wrote:
> Previously, the VS_OPCODE_PULL_CONSTANT_LOAD opcode operated on
> vec4-aligned byte offsets on Iron Lake and below and worked in terms of
> vec4 offsets on Sandy Bridge. On Ivy Bridge, we add a new *LOAD_GEN7
> variant which works in
Previously, the VS_OPCODE_PULL_CONSTANT_LOAD opcode operated on
vec4-aligned byte offsets on Iron Lake and below and worked in terms of
vec4 offsets on Sandy Bridge. On Ivy Bridge, we add a new *LOAD_GEN7
variant which works in terms of vec4s. We're about to change the GEN7
version to work in ter
Previously, the VS_OPCODE_PULL_CONSTANT_LOAD opcode operated on
vec4-aligned byte offsets on Iron Lake and below and worked in terms of
vec4 offsets on Sandy Bridge. On Ivy Bridge, we add a new *LOAD_GEN7
variant which works in terms of vec4s. We're about to change the GEN7
version to work in ter
