Re: [Nouveau] Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles

2015-07-24 Thread Ilia Mirkin
Indeed, this fixed the original issue on the GK208. Additionally it seems like starting with GK104 the mechanism for indirect offsets for ALD/AST changed and a AL2P instruction must now be used to determine the indirect or physical offset. Once nouveau was adjusted to do this, all

Re: [Nouveau] Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles

2015-07-23 Thread Ilia Mirkin
I think I figured out what was going on. Will re-check on the GK208, but on a GF108 the random blue splotches in Unigine Heaven are gone now. Turns out that with an instruction like /*00d0*/ ALD.128 R0, a[0x70], R0; /* 0x7ecc381ffc02 */ The hardware will

Re: [Nouveau] Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles

2015-05-26 Thread Ilia Mirkin
One additional observation that I just made is that on GK208, the blob apparently doesn't use the result of S2R Rx, SR_INVOCATION_ID wholesale in TCS. It either passes it through a I2I.S32.S32 Rx, |Rx| (i.e. absolute value), or even more paradoxically, shl 2; shr 2; which removes the top *2* bits,

Re: [Nouveau] Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles

2015-05-22 Thread Ilia Mirkin
On Mon, May 18, 2015 at 4:48 PM, Ilia Mirkin imir...@alum.mit.edu wrote: Hello, I've been debugging a few different tessellation shader issues with nouveau, but let's start small. I see this issue on my GK208 with high frequency, and I *think* I've seen it once or twice on my GF108, but it's

[Nouveau] Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles

2015-05-18 Thread Ilia Mirkin
Hello, I've been debugging a few different tessellation shader issues with nouveau, but let's start small. I see this issue on my GK208 with high frequency, and I *think* I've seen it once or twice on my GF108, but it's exceedingly rare, if it does happen. I don't have a GK10x to test on,