Thanks Chirs,
Yes that sounds right. I managed to get a core dump and it seems to be
an issue during linking with uniforms. Still trying to understand all
the code but the code in do_vs_prog() looks like a good starting point.
On Thu, 2014-01-16 at 10:00 +1300, Chris Forbes wrote:
> That assert m
That assert means that you've not told the backend the size of some
object correctly, and the register allocator has placed it so its true
extent hangs off the end of the available registers.
To fix it you'll need to adjust the code generation for array accesses
in i965 -- probably quite a bit.
O
First of all sorry for my first post being a reply to Ians 10.1 release
plan.
Secondly I've rebased my work on current master and reimplemented my
work using the approach I mention in my last email. The changes are half
the size and now some basic execution tests are passing. The new branch
is he
I think I've made things harder for my self than they need to be rather
than creating a glsl_type object to hold all the array information for
all dimensions I'm now thinking it would be simpler when processing the
ast to hir to just create a new type object for each dimension which
will then just
Hi all,
Its still a work in progress currently just passing the compile tests
that I submitted to the piglit list [1].
Its also a bit of a mess (some patches need squashing, a number of
patches are just temp updates to support single dimension arrays for the
time being) but I thought I would reque
