Age | Commit message (Collapse) | Author |
|
We don't set the type on the array virtual reg as a whole, so here's
the right place.
Fixes:
glsl1-GLSL 1.20 arrays
glsl1-temp array with constant indexing, fragment shader
glsl1-temp array with swizzled variable indexing
|
|
We need to re-run channel expressions afterwards as it generates new
vector expressions, and we need to successfully support conditional
assignment (brw_CMP takes 2 operands, not 1).
|
|
|
|
While much of this we will want to support natively, this should make
the task of reaching the Mesa IR backend's quality easier.
Fixes:
glsl-fs-main-return.
|
|
Fixes:
glsl-fs-if-nested-loop.
|
|
Fixes:
glsl1-Negation
glsl1-Negation2
|
|
Fix pipe control command for depth stall and PS_DEPTH_COUNT write.
|
|
Need to set point sprite function in fixed SF state now on sandybridge.
|
|
Fix incorrect scissor rect struct and missed scissor state pointer
setting for sandybridge.
|
|
Depth offset function is moved to SF stage on sandybridge.
|
|
|
|
Sandybridge doesn't have Xstart/Ystart in payload header.
|
|
Sandybridge's PS constant buffer payload size is decided from
push const buffer command, incorrect size would cause wrong data
in payload for position and vertex attributes. This fixes coefficients
for tex2d/tex3d.
|
|
Sandybridge has not much change on texture sampler with Ironlake.
|
|
Jump count is for 64bit long each, so one instruction requires 2
like on Ironlake.
|
|
Until conditional instructions were fixed, use SPF mode instead for now.
|
|
|
|
Sandybridge's VF would convert quads to polygon which not required
for GS then. Current GS state still would cause hang on lineloop.
|
|
|
|
|
|
|
|
Don't double store position in vertex attribute. This makes color
interpolation right by using barycentric coordinates.
|
|
Accumulator update flag must be set for implicit update on sandybridge.
|
|
Dump new state object on sandybridge for cc viewport, clip viewport,
depth stencil, cc and blend state.
|
|
|
|
Fixes glsl-algebraic-pow-2 in brw_wm_glsl.c mode.
|
|
Sending down data that doesn't get read doesn't make any sense, and
would make handling things like gl_FrontFacing and gl_PointCoord
harder.
|
|
Things are simpler these days thanks to barycentric interpolation
parameters being handed in in the payload.
|
|
Fixes:
glsl-fwidth
glsl-derivs-swizzle
|
|
Fixes:
glsl-fs-all-02
glsl-fs-dot-vec2
|
|
These are generated for scalar operands instead of plain equal/nequal.
But for scalars, they're the same anyway. +30 piglits.
|
|
We'd end up reading some non-x component of the float RHS. +53 piglits.
|
|
Not sure how I managed to get tests to succeed without this. +54 piglits.
|
|
Tested with fbo-generatemipmap-formats GL_EXT_texture_srgb. The test
still fails on SLA8, though.
|
|
Another optional ARB_imaging subset extension.
|
|
|
|
Fixes:
glsl1-precision exp2
glsl1-precision log2
|
|
The new checks for sanity in ir_assignment creation got angry about
this write_mask == 0. Fixes:
glsl-fs-dot-vec2.
glsl-fs-atan-2
glsl-fs-dot-vec2
|
|
+113 piglits.
|
|
Fix commit e7087175f8a04f777403366fb34b58edd00f4d60. Move the reference to
GL_VERSION_2_1_functions to intel_extensions.c where it's available,
don't try to enable a non-existing extension and advertise 1.20 for all
intel chipsets, not just GEN4 and up.
|
|
Instead of using the invalid GL_ARB_shading_language_120 extension to
determine the GLSL version, use a new ctx->Const.GLSLVersion field.
Updated the intel and r600 drivers, but untested.
See fd.o bug 29910
NOTE: This is a candidate for the 7.9 branch (but let's wait and see if
there's any regressions).
|
|
Looks like the problem was we weren't passing the depth to the render
target as expected, so the chip would wedge. Fixes GPU hang in
occlusion-query-discard.
Bug #30097
|
|
This is required by the spec, so respect that.
|
|
|
|
|
|
Fixes piglit tests glsl-vs-main-return and glsl-fs-main-return.
|
|
With recent changes to the GLSL compiler, these opcode should never be
seen in these drivers.
|
|
Fixes compiler warnings.
|
|
|
|
This increases the chance that GLSL programs will actually work.
Note that continues and returns are not yet lowered, so linking
will just fail if not supported.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|