URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=185ee6b612aca567dfaa31ae1be93e3385af4be4
Author: Nicolai Hähnle <[email protected]>
Date:   Tue Jan 19 15:18:31 2016 -0500

    radeonsi: fix discard-only fragment shaders (11.1 version)
    
    When a fragment shader is used that has no outputs but does conditional
    discard (KILL_IF), all fragments are killed without this patch.
    
    By comparing various register settings, my conclusion is that the exec mask
    is either not properly forwarded to the DB by NULL exports or ends up being
    unused, at least when there is _only_ a NULL export (the ISA documentation
    claims that NULL exports can be used to override a previously exported exec
    mask).
    
    Of the various approaches I have tried to work around the problem, this one
    seems to be the least invasive one.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93761
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=25fc54992e96886d71e5f266069ca21ac4828a4b
Author: Nicolai Hähnle <[email protected]>
Date:   Sat Jan 16 15:15:13 2016 -0500

    st/mesa: use the correct address generation functions in st_TexSubImage blit
    
    We need to tell the address generation functions about the dimensionality of
    the texture to correctly implement the part of Section 3.8.1 (Texture Image
    Specification) of the OpenGL 2.1 specification which says:
    
        "For the purposes of decoding the texture image, TexImage2D is
        equivalent to calling TexImage3D with corresponding arguments
        and depth of 1, except that
          ...
          * UNPACK SKIP IMAGES is ignored."
    
    Fixes a low impact bug that was found by chance while browsing the spec and
    extending piglit tests.
    
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Edward O'Callaghan <[email protected]>
    (cherry picked from commit 4a448a63adbbece1d9bddacd9428aad7cc68a628)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=37aed859693d5eee5e108d09deda249478cc07ec
Author: Leo Liu <[email protected]>
Date:   Mon Feb 1 13:32:31 2016 -0500

    st/omx/dec/h264: fix corruption when scaling matrix present flag set
    
    The scaling list should be filled out with zig zag scan
    
    v2: integrate zig zag scan for list 4x4 to vl(Christian)
    v3: move list determination out from the loop(Ilia)
    
    Cc: "11.0 11.1" <[email protected]>
    Signed-off-by: Leo Liu <[email protected]>
    Reviewed-by: Christian König <[email protected]>
    (cherry picked from commit 6ad2e55a1405ac3757439dae55ed86425bb65806)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3adf11182110f0e623c173d0658ae08b1012d6f6
Author: Leo Liu <[email protected]>
Date:   Mon Feb 1 12:04:34 2016 -0500

    vl: add zig zag scan for list 4x4
    
    Cc: "11.0 11.1" <[email protected]>
    Signed-off-by: Leo Liu <[email protected]>
    Reviewed-by: Christian König <[email protected]>
    (cherry picked from commit 4f598f2173c6555a52aad942ce6ea75c65afe21a)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f5f021ecc599fae8b668da76cd68a2b0e8c68cb2
Author: Ilia Mirkin <[email protected]>
Date:   Fri Jan 29 14:45:38 2016 -0500

    st/mesa: treat a write as a read for range purposes
    
    We use this logic to detect live ranges and then do plain renaming
    across the whole codebase. As such, to prevent WaW hazards, we have to
    treat a write as if it were also a read.
    
    For example, the following sequence was observed before this patch:
    
     13: UIF TEMP[6].xxxx :0
     14:   ADD TEMP[6].x, CONST[6].xxxx, -IN[3].yyyy
     15:   RCP TEMP[7].x, TEMP[3].xxxx
     16:   MUL TEMP[3].x, TEMP[6].xxxx, TEMP[7].xxxx
     17:   ADD TEMP[6].x, CONST[7].xxxx, -IN[3].yyyy
     18:   RCP TEMP[7].x, TEMP[3].xxxx
     19:   MUL TEMP[4].x, TEMP[6].xxxx, TEMP[7].xxxx
    
    While after this patch it becomes:
    
     13: UIF TEMP[7].xxxx :0
     14:   ADD TEMP[7].x, CONST[6].xxxx, -IN[3].yyyy
     15:   RCP TEMP[8].x, TEMP[3].xxxx
     16:   MUL TEMP[4].x, TEMP[7].xxxx, TEMP[8].xxxx
     17:   ADD TEMP[7].x, CONST[7].xxxx, -IN[3].yyyy
     18:   RCP TEMP[8].x, TEMP[3].xxxx
     19:   MUL TEMP[5].x, TEMP[7].xxxx, TEMP[8].xxxx
    
    Most importantly note that in the first example, the second RCP is done
    on the result of the MUL while in the second, the second RCP should have
    the same value as the first. Looking at the GLSL source, it is apparent
    that both of the RCP's should have had the same source.
    
    Looking at what's going on, the GLSL looks something like
    
      float tmin_8;
      float tmin_10;
      tmin_10 = tmin_8;
    ... lots of code ...
      tmin_8 = tmpvar_17;
    ... more code that never looks at tmin_8 ...
    
    And so we end up with a last_read somewhere at the beginning, and a
    first_write somewhere at the bottom. For some reason DCE doesn't remove
    it, but even if that were fixed, DCE doesn't handle 100% of cases, esp
    including loops.
    
    With the last_read somewhere high up, we overwrite the previously
    correct (and large) last_read with a low one, and then proceed to decide
    to merge all kinds of junk onto this temp. Even if that weren't the
    case, and there were just some writes after the last read, then we might
    still overwrite a merged value with one of those.
    
    As a result, we should treat a write as a last_read for the purpose of
    determining the live range.
    
    Signed-off-by: Ilia Mirkin <[email protected]>
    Reviewed-by: Dave Airlie <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 047b91771845453826dcdd0019adc7333348b158)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3ef2a4bb2eb4cec7ee00a7f78da7edc24ceb2a43
Author: François Tigeot <[email protected]>
Date:   Sun Jan 17 10:10:21 2016 +0100

    gallium: Add DragonFly support
    
    Cc: [email protected]
    Signed-off-by: Emil Velikov <[email protected]>
    (cherry picked from commit a48afb92ffda6e149c553ec82a05fee9a17441f8)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=12888ad942a3e5580d153ed37bbcb4e48ced6a04
Author: Ilia Mirkin <[email protected]>
Date:   Sat Jan 30 17:13:33 2016 -0500

    nv50/ir: fix false global CSE on instructions with multiple defs
    
    If an instruction has multiple defs, we have to do a lot more checks to
    make sure that we can move it forward. Among other things, various code
    likes to do
    
        a, b = tex()
        if () c = a
        else c = b
    
    which means that a single phi node will have results pointing at the
    same instruction. We obviously can't propagate the tex in this case, but
    properly accounting for this situation is tricky. Just don't try for
    instructions with multiple defs.
    
    This fixes about 20 shaders in shader-db, including the dolphin efb2ram
    shader.
    
    Signed-off-by: Ilia Mirkin <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 3ca941d60ed38800038cd545842e0ed3a69946da)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=0f7d3d661d1cc3a0f0c57468bc4a378cacf88b0b
Author: Ilia Mirkin <[email protected]>
Date:   Sat Jan 30 10:02:43 2016 -0500

    nv50,nvc0: fix buffer clearing to respect engine alignment requirements
    
    It appears that the nvidia render engine is quite picky when it comes to
    linear surfaces. It doesn't like non-256-byte aligned offsets, and
    apparently doesn't even do non-256-byte strides.
    
    This makes arb_clear_buffer_object-unaligned pass on both nv50 and nvc0.
    
    As a side-effect this also allows RGB32 clears to work via GPU data
    upload instead of synchronizing the buffer to the CPU (nvc0 only).
    
    Signed-off-by: Ilia Mirkin <[email protected]> # tested on GF108, GT215
    Tested-by: Nick Sarnie <[email protected]> # GK208
    Cc: [email protected]
    (cherry picked from commit 3ca2001b537a2709e7ef60410e7dfad5d38663f4)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=7cb93f77f217b323a429e343c695ddc96d6970ab
Author: Ilia Mirkin <[email protected]>
Date:   Fri Jan 29 20:28:12 2016 -0500

    nvc0: avoid crashing when there are holes in vertex array bindings
    
    When using the "shared" vertex array configuration strategy, we bind
    each of the buffers as a separate array. However there can be holes in
    such vertex buffer lists, so just emit a disable for those.
    
    Signed-off-by: Ilia Mirkin <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 438d421f8bb3f65402701628c3504c0ad04184c0)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=03eb1716dda2ebc06d7c8395374658953138b438
Author: Eric Anholt <[email protected]>
Date:   Tue Jan 26 10:34:42 2016 -0800

    vc4: Throttle outstanding rendering after submission.
    
    Just make sure that after we've submitted, we get to at least 5
    (global) submits ago before we go on to do more.  Prevents up to
    seconds of lag with window movement in X with xcompmgr -c.  There may
    be useful tuning to do in the future, but for now this gets us
    usability.
    
    Cc: "11.0 11.1" <[email protected]>
    Signed-off-by: Eric Anholt <[email protected]>
    (cherry picked from commit 3fba517bdd03551f7c7ff21dfe1896c677cbccda)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4865ab2b4334e7b4f4f1fe30a6a333234a86f06b
Author: Eric Anholt <[email protected]>
Date:   Tue Jan 26 10:28:45 2016 -0800

    vc4: Don't record the seqno of a failed job submit.
    
    On an error return, the returned seqno will probably be unset, so we'd
    lose track of what we've submitted so far for waiting on in the
    future.
    
    Cc: "11.0 11.1" <[email protected]>
    Signed-off-by: Eric Anholt <[email protected]>
    (cherry picked from commit 2a449ce7c961f3269f9a37ddf4fe340fc170c609)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=045e269a92a0ba1166a839b23e3751b91d20057c
Author: Karol Herbst <[email protected]>
Date:   Tue Jan 26 14:36:04 2016 +0100

    nv50/ir: fix memory corruption when spilling and redoing RA
    
    When RA fails, and we spill, we have to clean everything up before doing
    RA again. We were forgetting to reset the hi/lo linked lists - at
    least the hi list is guaranteed to still have pointers to now-deleted
    RIG nodes.
    
    Signed-off-by: Karol Herbst <[email protected]>
    Reviewed-by: Ilia Mirkin <[email protected]>
    Cc: [email protected]
    (cherry picked from commit 19ae5de981e014e1b366b4652e14eb1ea0421574)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=761e3fda6e23d04e15e1716c2557c3da81f55539
Author: Ben Widawsky <[email protected]>
Date:   Mon Jan 25 11:49:10 2016 -0800

    i965/bxt: Fix conservative wm thread counts.
    
    When setting the conservative thread counts, I halved everything. That isn't
    correct for the wm, which has nothing to do with actual thread counts. I 
suck.
    
    BXT only has 1 slice, and there is some ambiguity about subslices, so just
    reserve the max possible for now. It looks like this might fix:
    
piglit.spec.glsl-1_50.execution.variable-indexing.gs-output-array-vec4-index-wr.bxtm64.
    I kind of question why that is, but it is what Jenkins says.
    
    Mark is current running some of the other blacklisted tests on this patch. 
(it
    effects anything requiring scratch space).
    
    Cc: mesa-stable <[email protected]>
    Cc: Neil Roberts <[email protected]>
    Signed-off-by: Ben Widawsky <[email protected]>
    Acked-by: Kenneth Graunke <[email protected]>
    Tested-by: Mark Janes <[email protected]>
    (cherry picked from commit a443b5b7320ef0d8a63faf8a7fc6136f97460cea)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=7e1bd26d5423f23c7cf931ef0ccd3d4c37224ace
Author: Ian Romanick <[email protected]>
Date:   Tue Jan 12 16:37:27 2016 -0800

    meta: Use internal functions to set texture parameters
    
    _mesa_texture_parameteriv is used because (the more obvious)
    _mesa_texture_parameteri just stuffs the parameter in an array and calls
    _mesa_texture_parameteriv.  This just cuts out the middleman.
    
    As a side bonus we no longer need check that ARB_stencil_texturing is
    supported.  The test doesn't allow non-supporting implementations to
    avoid any work, and it's redundant with the value-changed test.
    
    Fix bug #93717 because the state restore commands at the bottom of
    _mesa_meta_GenerateMipmap no longer depend on the bound state.
    
    Fixes  piglit   arb_direct_state_access-generatetexturemipmap  with  the
    changes  recently sent  to the  piglit mailing  list.  See  the bugzilla
    entry for more info.
    
    Signed-off-by: Ian Romanick <[email protected]>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93717
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Jason Ekstrand <[email protected]>
    (cherry picked from commit 2542871387393e855f6afe6c94d44611eefaf6eb)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e5d37f16e03420e56a143b3c04dbc575afd8a4d2
Author: Ian Romanick <[email protected]>
Date:   Tue Jan 12 16:08:47 2016 -0800

    meta/blit: Restore GL_DEPTH_STENCIL_TEXTURE_MODE state for 
GL_TEXTURE_RECTANGLE
    
    Commit c246828c added the code to save and restore the stencil
    texturing mode.  The restore, however, was erroneously inside the
    'target != GL_TEXTURE_RECTANGLE' block.
    
    Fixes piglit test 'arb_stencil_texturing-blit_corrupts_state
    GL_TEXTURE_RECTANGLE'.
    
    Signed-off-by: Ian Romanick <[email protected]>
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Jason Ekstrand <[email protected]>
    (cherry picked from commit 18b0ba340b9229e7afd5e38b5d825fde3a435b63)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e22133f1bfdcffeb88f1b8c7c9e0549bfc4f10a6
Author: Nicolai Hähnle <[email protected]>
Date:   Sun Jan 24 11:16:34 2016 -0500

    radeonsi: add DCC buffer for sampler views on new CS
    
    This fixes a VM fault and possible lockup in high memory pressure 
situations.
    
    Cc: "11.1" <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    Reviewed-by: Edward O'Callaghan <[email protected]>
    (cherry picked from commit 1067e6eb552ac850258e33e4eba689a964581c8a)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=6dbb144b3da5a8022f9ea81d7e55d6b508b8ced9
Author: Nicolai Hähnle <[email protected]>
Date:   Fri Jan 22 17:04:48 2016 -0500

    radeonsi: ensure that VGT_GS_MODE is sent when necessary
    
    Specifically, when the API switches from using a GS to not using a GS and 
then
    back to using the same GS again, we do not have to re-send all the GS state,
    but we do have to send VGT_GS_MODE. So make VGT_GS_MODE consistently be a 
part
    of the VS state.
    
    This fixes a rendering bug in Dolphin, but surely other applications are
    affected as well.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93648
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Edward O'Callaghan <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit 004fcd423011d45f746d571be47062feeea75455)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4ba352dc80cd55afcc0b81866168f2354fc73600
Author: Nicolai Hähnle <[email protected]>
Date:   Fri Jan 22 16:58:15 2016 -0500

    radeonsi: extract the VGT_GS_MODE calculation into its own function
    
    Cc: "11.0 11.1" <[email protected]>
    Reviewed-by: Edward O'Callaghan <[email protected]>
    Reviewed-by: Marek Olšák <[email protected]>
    (cherry picked from commit 9f89bd69df4a32eb1a7ebaf8bbd2c463f1a7882f)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e101a005b14ee36568a12e2cf08c734be167cf23
Author: Ilia Mirkin <[email protected]>
Date:   Thu Jan 21 07:17:06 2016 -0500

    glsl: always compute proper varying type, irrespective of varying packing
    
    Normally there's a producer and consumer, and the producer var gets
    picked. In both the vertex->gs and tes->gs cases, that's the un-arrayed
    version.
    
    In the SSO case, however, there is no producer. So we picked the arrayed
    GS variable, and as a result, used more slots than we should. More
    critically, these slots would also no longer line up with the producer's
    calculation. To fix this, we need to fix up the type of the variable
    based on stage no matter what.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93650
    Signed-off-by: Ilia Mirkin <[email protected]>
    Reviewed-by: Timothy Arceri <[email protected]>
    Cc: "11.0 11.1" <[email protected]>
    (cherry picked from commit dac2964f3ebd96d5ac227984ab0cd79c2c3b2a1a)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=65dfe8ba5fda1bdf154a709f58342b80afb1be25
Author: Timothy Arceri <[email protected]>
Date:   Fri Dec 18 13:53:27 2015 +1100

    glsl: create helper to remove outer vertex index array used by some stages
    
    This will be used in the following patch for calculating array sizes 
correctly
    when reserving explicit varying locations.
    
    Reviewed-by: Anuj Phogat <[email protected]>
    Reviewed-by: Edward O'Callaghan <[email protected]>
    (cherry picked from commit 5907a02ab6fbe20b4ba58eb00bf93261129798d5)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=ae0733e2a171958e94a63e67d7cece8c28432a73
Author: Emil Velikov <[email protected]>
Date:   Sun Nov 29 16:48:51 2015 +0000

    egl/dri2: expose srgb configs when KHR_gl_colorspace is available
    
    Otherwise the user has no way of using it, and we'll try to access the
    linear one.
    
    v2:
     - Bail out when KHR_gl_colorspace is missing and srgb is set (Marek)
    
    Cc: Chih-Wei Huang <[email protected]>
    Cc: "11.0 11.1" <[email protected]>
    Fixes: c2c2e9ab604(egl: implement EGL_KHR_gl_colorspace (v2))
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91596
    Signed-off-by: Emil Velikov <[email protected]>
    Tested-by: Mauro Rossi <[email protected]>
    (cherry picked from commit 54702c2fa1a146f45a1f8c35abe2b529e24b2acf)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e8ae0e75fe5db8232937aaeb55945f296cfd0526
Author: Emil Velikov <[email protected]>
Date:   Sun Nov 29 16:38:54 2015 +0000

    targets/dri: android: use WHOLE static libraries
    
    By using whole static libraries the android buildsystem provides
    whole-archive (alike) solution. This means that we don't need to worry
    about the order of the static libraries and any reverse, recursive or
    circular dependencies that they have between one another.
    
    Without this the linker will discard any unused hunks of one library
    and we'll end up with unresolved symbols as those are required by
    another static library. This issue has become more prominent with the
    introduction of pipe-loader.
    
    Whole static libraries has been used in i915/i965 for a very long
    time, so we might do the same.
    
    v2:
     - Better commit message (Ilia)
     - Keep external dependencies as [normal] static libs (Mauro)
    
    Cc: [email protected]
    Cc: Mauro Rossi <[email protected]>
    Reported-by: Mauro Rossi <[email protected]>
    Signed-off-by: Emil Velikov <[email protected]>
    (cherry picked from commit f29a772a7e0ae5113822bcf14eb3bc87477c5fb1)

URL:    
http://cgit.freedesktop.org/mesa/mesa/commit/?id=6e86513db9edcda77b1f6f5a870b0dece0d0ee65
Author: Emil Velikov <[email protected]>
Date:   Fri Dec 18 15:28:03 2015 +0000

    i915: correctly parse/set the context flags
    
    With an earlier commit we've spit the flags parsing to a separate
    function, but forgot to update all the dri modules to use it.
    
    Noticed when we've enabled KHR_debug for every dri module - fdo#93048
    
    Fixes: 38366c0c6e7 "dri_util: Don't assume __DRIcontext->driverPrivate
    is a gl_context"
    Cc: Mark Janes <[email protected]>
    Cc: "11.0 11.1" <[email protected]>
    Cc: Kristian Høgsberg <[email protected]>
    Cc: Ian Romanick <[email protected]>
    Signed-off-by: Emil Velikov <[email protected]>
    Reviewed-by: Mark Janes <[email protected]>
    Tested-by: Mark Janes <[email protected]>
    
    (cherry picked from commit 72fda2b710d864d23aec1e8f959147d05c5ff3f3)

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

Reply via email to