URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=5e0b11cb6dbeab7ca6a1ba2edca56701cdfde96c
Author: Emil Velikov <[email protected]>
Date:   Tue Jun 21 13:32:04 2016 +0100

    Update version to 12.0.0-rc4
    
    Signed-off-by: Emil Velikov <[email protected]>

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=6306930c3f0cd790e9d8995468559453b6c75b2c
Author: Nicolai Hähnle <[email protected]>
Date:   Fri Jun 10 15:59:58 2016 +0200

    st/mesa: flush bitmap cache before CopyImageSubData
    
    Found by inspection.
    
    Cc: 11.2 12.0 <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit f9ddd52317caf14a21ec7c040fd4bb944f9842e4)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=76377387c2d44d0fbae21763386ac86ffb54c635
Author: Nicolai Hähnle <[email protected]>
Date:   Thu Jun 9 12:22:31 2016 +0200

    st/mesa: flush bitmap cache before texture functions
    
    As far as I can tell, a sequence of glBitmap followed by texture functions
    that refer to a texture bound as the framebuffer is well within what should
    be allowed.
    
    Found by inspection.
    
    Cc: 11.2 12.0 <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit e7fff3cfe156e13198107e5e76a77fb79ed02173)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=6775b169cdffecd373d57847e5d71db3fe39409a
Author: Nicolai Hähnle <[email protected]>
Date:   Thu Jun 9 12:12:34 2016 +0200

    st/mesa: flush bitmap cache before compute dispatch
    
    In the unlikely case that a program uses glBitmap to render to a framebuffer
    whose texture is bound in a compute shader.
    
    Found by inspection.
    
    Cc: 11.2 12.0 <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit c542b7e43d3a504456518c9f407e21c4e7e5fa88)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a0235eb0f716e05c290cad66292b703c2178af91
Author: Kenneth Graunke <[email protected]>
Date:   Wed Jun 8 16:09:02 2016 -0700

    i965: Fix multiplication of immediates on Cherryview/Broxton.
    
    Cherryview and Broxton don't support DW x DW multiplication.  We have
    piles of code to handle this, but apparently weren't retyping in the
    immediate case.
    
    For example,
    tests/spec/arb_tessellation_shader/execution/dvec3-vs-tcs-tes
    makes the simulator angry about instructions such as:
    
       mul(8) r18<1>:D r10.0<8;8,1>:D 0x00000003:D
    
    Just retype to W or UW.  It should be safe on all platforms.
    
    Cc: "12.0" <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95462
    Reviewed-by: Matt Turner <[email protected]>
    Reviewed-by: Jordan Justen <[email protected]>
    Signed-off-by: Kenneth Graunke <[email protected]>
    (cherry picked from commit cd89c834a8b3b4e5f5874c8e1f90c9b01d541181)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=09a098bdeb89baacd6bbadc4180daf9c2ffaa840
Author: Jason Ekstrand <[email protected]>
Date:   Tue Jun 14 08:40:49 2016 -0700

    anv: Add proper support for depth clamping
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit eb6764c4a73006eee32e19e3afc6eab100a2ce16)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f3c8dde2e4cac98ab190c0378e20424f0b59d9ef
Author: Jason Ekstrand <[email protected]>
Date:   Tue Jun 14 08:15:34 2016 -0700

    anv/cmd_buffer: Split emit_viewport in two
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit 8a46b505cb2c7255ad430b56c1ce0dfa9c13c559)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3fddb9fd46a6066d8ecf0bd19a370acbbbc05b2b
Author: Jason Ekstrand <[email protected]>
Date:   Mon Jun 13 17:09:37 2016 -0700

    anv/cmd_buffer: Set depth/stencil extent based on the image
    
    It used to be based on the framebuffer which isn't quite right.
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit 20e95a746df34923eb4aac5e7f1ab6d722432d89)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f614a1f4d88d02f429f29a4e95596e4a40ba7cce
Author: Jason Ekstrand <[email protected]>
Date:   Wed Jun 15 14:30:33 2016 -0700

    anv/cmd_buffer: Don't crash if push constants are provided for missing 
stages
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit b65f2e4163c9180e6a022c0afec018b08e4c5aa5)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f4bc7218d59d55825c4ab2b76e6134827f10d401
Author: Jason Ekstrand <[email protected]>
Date:   Thu Jun 16 10:57:39 2016 -0700

    anv/pipeline: Do invariance propagation on SPIR-V shaders
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit e6c2fe451962e364f30f689dc48c34e2b6161b25)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=77f241bd37e7d0a76a0ac9223bc4cebba322994c
Author: Jason Ekstrand <[email protected]>
Date:   Mon Jun 13 14:41:05 2016 -0700

    nir/alu_to_scalar: Respect the exact ALU operation qualifier
    
    Just setting builder->exact isn't sufficient because that only applies to
    instructions that are built with the builder but instructions created
    manually and only inserted using the builder are left alone.
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit bec07b729242f6a2dcf5a12ce75bf8b07ea658e0)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=deedb368de7dc50f7196af440c338dcf6a361564
Author: Jason Ekstrand <[email protected]>
Date:   Mon Jun 13 12:47:19 2016 -0700

    nir: Add a pass for propagating invariant decorations
    
    This pass is similar to propagate_invariance in the GLSL compiler.  The
    real "output" of this pass is that any algebraic operations which are
    eventually consumed by an invariant variable get marked as "exact".
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    Cc: "12.0" <[email protected]>
    (cherry picked from commit 202751fbb7e3d35c1aa84f325f862245dab67f6c)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=bac23b13eb75a7bacdec439eb4c239a8dedb24e7
Author: Jason Ekstrand <[email protected]>
Date:   Sat Jun 18 12:30:36 2016 -0700

    nir/algebraic: Remove imprecise flog2 optimizations
    
    While mathematically correct, these two optimizations result in an
    expression with substantially lower precision than the original.  For any
    positive finite floating-point value, log2(x) is well-defined and finite.
    More precisely, it is in the range [-150, 150] so any sum of logarithms
    log2(a) + log2(b) is also well-defined and finite as long as a and b are
    both positive and finite.  However, if a and b are either very small or
    very large, their product may get flushed to infinity or zero causing
    log2(a * b) to be nowhere close to log2(a) + log2(b).
    
    This imprecision was causing incorrect rendering in Talos Principal because
    part of its HDR rendering process involves doing 8 texture operations,
    clamping the result to [0, 65000], taking a dot-product with a constant,
    and then taking the log2.  This is done 6 or 8 times and summed to produce
    the final result which is written to a red texture.  In cases where you
    have a region of the screen that is very dark, it can end up getting a
    result value of -inf which is not what is intended.
    
    Signed-off-by: Jason Ekstrand <[email protected]>
    Reviewed-by: Matt Turner <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96425
    Cc: "11.1 11.2 12.0" <[email protected]>
    (cherry picked from commit 68e308d85355079ad93bd4e16cba164784740fdf)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=b03b256e921c3f7cebfcf9efd5bdf7b403b9c961
Author: Nicolai Hähnle <[email protected]>
Date:   Fri Jun 17 10:48:53 2016 +0200

    radeonsi: fix calculation of valid RB mask per SE
    
    The old calculation treated too many RBs as disabled.
    
    Cc: 11.0 11.1 11.2 12.0 <[email protected]>
    Reviewed-by: Alex Deucher <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit c95175581e983642dc4b23d059e6eaff5b79d2db)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=52ae654569cb1e0e42f12b492fdd62d7cf20dc12
Author: Nicolai Hähnle <[email protected]>
Date:   Fri Jun 17 10:30:44 2016 +0200

    radeonsi: raise SI_PM4_MAX_DW
    
    The old limit, introduced in commit 
afa752d3f03ac6697581ff5d324e8ac0512ef513,
    was exceeded by 4 SE configurations which hit 
si_write_harvested_raster_configs.
    
    Cc: 11.1 11.2 12.0 <[email protected]>
    Reviewed-by: Alex Deucher <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit 6c2e63698290d3ea868eefcc3e4dd51dc1e16c64)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f675339b224b90cac161840716fcc348926f88c7
Author: Roland Scheidegger <[email protected]>
Date:   Sun Jun 19 03:56:11 2016 +0200

    gallivm: don't use integer min/max sse intrinsics with llvm >= 3.9
    
    Apparently, these are deprecated. There's some AutoUpgrade feature which
    is supposed to promote these to cmp/select, which apparently doesn't work
    with jit code. It is possible it's not actually even meant to work (see
    the bug filed against llvm which couldn't provide an answer neither)
    but in any case this is meant to be only temporary unless the intrinsics
    are really illegal. So, just use the fallback code (which should be 
cmp/select,
    we're actually doing cmp/sext/trunc/select, but in any case llvm 3.9 manages
    to optimize this back to pmin/pmax in the end).
    
    This addresses https://llvm.org/bugs/show_bug.cgi?id=28176
    
    CC: <[email protected]>
    
    Reviewed-by: Jose Fonseca <[email protected]>
    Tested-by: Vinson Lee <[email protected]>
    Tested-by: Aaron Watry <[email protected]>
    (cherry picked from commit b0cf99165af445adc4c5c1f66a3a3e0d882211cd)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=cdbcd315b337f3cd7eb76d0d9771113b527e5940
Author: Ilia Mirkin <[email protected]>
Date:   Sun Jun 19 00:28:36 2016 -0400

    nvc0: don't make use of push hint if there are no non-const user vbos
    
    This makes the check match up what we do on nv50 as well - there's no
    point in switching over the push path if everything's in managed
    buffers. This can happen when a shader uses a vertex without an enabled
    array - we end up passing it a constant attribute.
    
    This also has the effect of "fixing" some flickering in Talos. I have no
    idea why. I've stared at the push logic forwards, backwards, and
    sideways. By always forcing the push path (which is slow), the
    flickering also goes away, but other rendering is still wrong
    (specifically draw 383068 as identified in the bug). However by not
    switching over to the push path, draw 383068 is correct.
    
    Note that other flickering remains in Talos, like the red/green
    walls/floors. This takes care of the shadow flickering though.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90513
    Signed-off-by: Ilia Mirkin <[email protected]>
    Cc: "12.0" <[email protected]>
    Reviewed-by: Samuel Pitoiset <[email protected]>
    (cherry picked from commit 154c0a42a23187c61ea0a1307198fae667398eba)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=7f1a4dc7405e2b21f68f624d3885518870b4248b
Author: Ilia Mirkin <[email protected]>
Date:   Sat Jun 18 15:22:09 2016 -0400

    gk104/ir: fix tex use generation to be more careful about eliding uses
    
    If we have a loop, instructions before the tex might be added as tex
    uses, and those may in fact dominate all other uses of the tex results.
    This however doesn't mean that we don't need a texbar after the tex.
    Only check if uses dominate each other they are dominated by the tex.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96565
    Fixes: 7752bbc44 (gk104/ir: simplify and fool-proof texbar algorithm)
    Signed-off-by: Ilia Mirkin <[email protected]>
    Cc: "11.2 12.0" <[email protected]>
    Reviewed-by: Samuel Pitoiset <[email protected]>
    (cherry picked from commit 1804aa0b80cf5b1ee5d97bc33a12808c78673a12)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=97440cc2ed686f54322d8ac99b88339baf1e91ac
Author: Samuel Iglesias Gonsálvez <[email protected]>
Date:   Mon Jun 13 08:29:53 2016 +0200

    i965/fs: indirect addressing with doubles is not supported in CHV/BSW/BXT
    
    From the Cherryview's PRM, Volume 7, 3D Media GPGPU Engine, Register Region
    Restrictions, page 844:
    
      "When source or destination datatype is 64b or operation is integer DWord
       multiply, indirect addressing must not be used."
    
    v2:
    - Fix it for Broxton too.
    
    v3:
    - Simplify code by using subscript() and not creating a new num_components
    variable (Kenneth).
    
    Signed-off-by: Samuel Iglesias Gonsálvez <[email protected]>
    Cc: "12.0" <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95462
    Reviewed-by: Kenneth Graunke <[email protected]>
    (cherry picked from commit bdab572a86f27b92ba10124f85d278e9c8861fff)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3265becac31005e093b1c89ceed683e094558e11
Author: Iago Toral Quiroga <[email protected]>
Date:   Mon Jun 13 03:13:23 2016 -0400

    i965/fs: Fix single-precision to double-precision conversions for 
CHV/BSW/BXT
    
    From the Cherryview PRM, Volume 7, 3D Media GPGPU Engine,
    Register Region Restrictions:
    
       "When source or destination is 64b (...), regioning in Align1
        must follow these rules:
    
        1. Source and destination horizontal stride must be aligned to
           the same qword.
        (...)"
    
    v2:
    - Fix it for Broxton too.
    
    v3:
    - Remove inst->regs_written change as it is not necessary (Ken)
    
    Cc: "12.0" <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95462
    Tested-by: Mark Janes <[email protected]>
    Reviewed-by: Kenneth Graunke <[email protected]>
    (cherry picked from commit 0177dbb6c2fe876a9761a4a97eec44accfa4c007)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=033279c9616b49221ce4b235b04dce62b015e0d2
Author: Ian Romanick <[email protected]>
Date:   Mon Jun 13 09:59:10 2016 -0700

    mesa: If validation fails in a debug context just emit a debug message
    
    There are quite a few pipelines that desktop applications (including a
    bunch of piglit test) can expect to have run but don't meet the GLES
    requirements.  Instead of failing validation, just emit a debug message.
    
    Signed-off-by: Ian Romanick <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96358
    Cc: "12.0" <[email protected]>
    Cc: Gregory Hainaut <[email protected]>
    Reviewed-by: Ilia Mirkin <[email protected]>
    Reviewed-by: Timothy Arceri <[email protected]>
    (cherry picked from commit 6bec55a780b0e95445c6d77c6e35cc0c74290ac0)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=65722736318525098d69be883977a034efd9940e
Author: Ian Romanick <[email protected]>
Date:   Mon Jun 13 15:22:34 2016 -0700

    glsl: Always strip arrayness in precision_qualifier_allowed
    
    Previously some callers of precision_qualifier_allowed would strip the
    arrayness from the type and some would not.  As a result, some places
    would not notice that float[6], for example, needed a precision
    qualifier.
    
    Fixes the new piglit test no-default-float-array-precision.frag.
    
    Signed-off-by: Ian Romanick <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96358
    Cc: "12.0" <[email protected]>
    Cc: Gregory Hainaut <[email protected]>
    Cc: Ilia Mirkin <[email protected]>
    Reviewed-by: Timothy Arceri <[email protected]>
    (cherry picked from commit 9c872820413f6183db0eb47828a7afcf703f9930)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=dab4a6001b2fc312571bfc8ee48ec08049946ebc
Author: Kenneth Graunke <[email protected]>
Date:   Wed Jun 1 00:08:55 2016 -0700

    i965: Use a uniform for gl_PatchVerticesIn in the TCS on Gen8+.
    
    We still need to recompile the passthrough shader when this value
    changes, as it also affects the output vertex count.  But otherwise,
    we can eliminate recompiles on Gen8+.
    
    We probably want to do this for Gen7 as well, but that requires
    rewriting the input release code to use a loop, which is a trade-off
    I'd need to consider in more detail.
    
    Signed-off-by: Kenneth Graunke <[email protected]>
    Reviewed-by: Alejandro Piñeiro <[email protected]>
    Cc: [email protected]
    (cherry picked from commit c319512e16f19bf1f558670981bbb4af510ba9f4)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=286ed3aff064768a816edc6d31ebede8c47b6e52
Author: Kenneth Graunke <[email protected]>
Date:   Thu May 26 20:21:58 2016 -0700

    glsl: Optionally lower TCS gl_PatchVerticesIn to a uniform.
    
    i965 has no special hardware for this, so the best way to implement
    this is to pass it in via a uniform.
    
    Signed-off-by: Kenneth Graunke <[email protected]>
    Reviewed-by: Alejandro Piñeiro <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 2b867264d2cce59bd65bd3599ff0e3c5439bc9d4)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=baa6ef4ed08ca8eb23a5368ab6f8ceb5e8c9c3d5
Author: Kenneth Graunke <[email protected]>
Date:   Wed Jun 1 00:08:55 2016 -0700

    i965: Use a uniform for gl_PatchVerticesIn in the TES.
    
    Fixes three GL44-CTS.tessellation_shader subtests:
    - max_patch_vertices
    - single.max_patch_vertices
    - tessellation_control_to_tessellation_evaluation.gl_PatchVerticesIn
    
    These use gl_PatchVerticesIn in the TES, but don't link against a
    TCS (which would allow the linker to lower it to a constant).  We had
    no handling for the system value in the backend, so it would just
    assert fail.
    
    Signed-off-by: Kenneth Graunke <[email protected]>
    Reviewed-by: Alejandro Piñeiro <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 1bc194cd64085d07f1aae319cb6fb3c99d69aaeb)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=b7e91a0421d3b1e29e224b32cfd2a95bd8593e19
Author: Kenneth Graunke <[email protected]>
Date:   Thu May 26 20:21:58 2016 -0700

    glsl: Optionally lower TES gl_PatchVerticesIn to a uniform.
    
    i965 has no special hardware for this, so we need to pass this value in
    as a uniform (unless the TES is linked against a TCS, in which case the
    linker can just replace this with a constant).
    
    Signed-off-by: Kenneth Graunke <[email protected]>
    Reviewed-by: Alejandro Piñeiro <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 0be210513797d3a0245588df915b9510c201bea4)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=05c5ed47d1878eb3933960aa485573c5091e2737
Author: Nicolai Hähnle <[email protected]>
Date:   Fri May 13 01:48:04 2016 -0500

    mesa/main: fix integer overflows in _mesa_image_offset
    
    Found using -fsanitize=undefined.
    
    Cc: "11.1 11.2 12.0" <[email protected]>
    Reviewed-by: Brian Paul <[email protected]>
    (cherry picked from commit 6510e0734563ff8d30e45b8781153367db15cc5b)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a9647850d16bcf7a3204d2889783fd733f896718
Author: Kenneth Graunke <[email protected]>
Date:   Thu May 26 19:56:48 2016 -0700

    mesa: Pass gl_constant_value union into _mesa_fetch_state().
    
    We've had some trouble in the past with copying integers around via
    float pointers, as the C compiler sometimes uses x87 floating point
    registers to load values on 32-bit systems.  Passing the
    gl_constant_value union should be safer.
    
    To avoid churn, this patch creates a "GLfloat *value" variable so
    existing uses can stay the same.
    
    Not observed to fix anything, but I was in the area adding more integer
    state vars, and thought it'd be wise.
    
    Signed-off-by: Kenneth Graunke <[email protected]>
    Reviewed-by: Dave Airlie <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 8b408972ff5476f1e23ad24a329f89442e6df054)

_______________________________________________
mesa-commit mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-commit

Reply via email to