{"push_id":1031294201,"size":87,"distinct_size":6,"ref":"refs/heads/ARB_clear_texture-radeonsi","head":"5e7a391076c3e229234cf4cbe71c8d381a5d0948","before":"1d54fa61ffbc38cc0ca162448e5a01bcf6b1c90b","commits":[{"sha":"e05492fd7f0e1a9454482a9174f5870b8cb5a41e","author":{"email":"506e97eed81d9e59d22f4c73fb51123bb62b4a30@gmail.com","name":"Samuel Pitoiset"},"message":"nv50/ir: fix compilation warning in handleSharedATOM()\n\nIn release build mode only, op may be used uninitialized because\nthe assertion has been removed.\n\nSigned-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nReviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/e05492fd7f0e1a9454482a9174f5870b8cb5a41e"},{"sha":"d86933e6f42b9c2f5bb617c66c91795c560a9abd","author":{"email":"506e97eed81d9e59d22f4c73fb51123bb62b4a30@gmail.com","name":"Samuel Pitoiset"},"message":"nv50,nvc0: replace resInfoCBSlot by auxCBSlot\n\nHaving two different variables for the driver constant buffer slot\nis confusing and really useless.\n\nSigned-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nAcked-by: Ilia Mirkin <imirkin@alum.mit.edu>\nAcked-by: Pierre Moreau <pierre.morrow@free.fr>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/d86933e6f42b9c2f5bb617c66c91795c560a9abd"},{"sha":"26cc411db87f924003f227874d7a047dd8b5e5a4","author":{"email":"506e97eed81d9e59d22f4c73fb51123bb62b4a30@gmail.com","name":"Samuel Pitoiset"},"message":"nv50/ir: make use of auxCBSlot instead of magic numbers\n\nThis avoids using magic numbers for the driver constbuf slot which\nis always 15 except for compute shaders on gk104+ where the slot 0\nis used.\n\nFor gk104+, some special compute-related values like the thread\nindex are uploaded to screen->parm which is currently bound on c0.\n\nSigned-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nAcked-by: Ilia Mirkin <imirkin@alum.mit.edu>\nAcked-by: Pierre Moreau <pierre.morrow@free.fr>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/26cc411db87f924003f227874d7a047dd8b5e5a4"},{"sha":"902bbda81b31bacb2a8c60ca6a8ba8ca34ae73d3","author":{"email":"506e97eed81d9e59d22f4c73fb51123bb62b4a30@gmail.com","name":"Samuel Pitoiset"},"message":"nvc0: avoid using magic numbers for the uniform_bo offsets\n\nInstead make use of constants to improve readability.\n\nThe first 32 bytes of the driver constant buffer are unknown... This\ndoesn't seem to be used in the codegen part, but if the texBindBase\noffset is shifted from 0x20 to 0x00, this breaks the universe for\nreally weird reasons. This sounds like to be related to textures.\n\nAnyway, name this NVC0_CB_AUX_UNK_INFO and add a todo should be\nenough for now.\n\nSigned-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nAcked-by: Ilia Mirkin <imirkin@alum.mit.edu>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/902bbda81b31bacb2a8c60ca6a8ba8ca34ae73d3"},{"sha":"d1b85dbffa0eec2b44bb2a9f339a2617a39730da","author":{"email":"bcbbb7aa705ec3a5fc5824c01a845186c3d62fca@alum.mit.edu","name":"Ilia Mirkin"},"message":"nv50: reset TFB bufctx when we no longer hold a reference to the buffers\n\nThis fix is analogous to commit ff085d014.\n\nThis fixes some use-after-free situations in dEQP when an xfb state is\nremoved, and then a clear is triggered, which only does a partial\nvalidation. It would attempt to read the no-longer-valid buffers,\nresulting in crashes.\n\nSigned-off-by: Ilia Mirkin <imirkin@alum.mit.edu>\nReviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/d1b85dbffa0eec2b44bb2a9f339a2617a39730da"},{"sha":"d2445b00837c9123b59a1ac743c136546f334504","author":{"email":"bcbbb7aa705ec3a5fc5824c01a845186c3d62fca@alum.mit.edu","name":"Ilia Mirkin"},"message":"nv50/ir: force-enable derivatives on TXD ops\n\nThis matters especially in vertex shaders, where derivatives are\ndisabled by default. This fixes textureGrad in vertex shaders on nv50.\n\nSigned-off-by: Ilia Mirkin <imirkin@alum.mit.edu>\nReviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/d2445b00837c9123b59a1ac743c136546f334504"},{"sha":"789e0965941533b0eeb2bc822012985e7c36d9c9","author":{"email":"bd2562f754ec92342f93f61c25d731e290a2ffa8@whitecape.org","name":"Kenneth Graunke"},"message":"mesa: Disallow GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME on winsys FBO.\n\nFixes:\ndEQP-GLES3.functional.negative_api.state.get_framebuffer_attachment_parameteriv\n\nApparently, GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME is not allowed when\nGL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is GL_FRAMEBUFFER_DEFAULT, and\nis expected to result in a GL_INVALID_ENUM error.\n\nNo GL specification actually defines what GL_FRAMEBUFFER_DEFAULT means.\nIt probably means the window system FBO.  It also doesn't mention the\nbehavior of any queries for that type.  Various ARB folks seem fairly\nconfused about it too.  For now, just do something vaguely like what\ndEQP expects.\n\nI think we probably need to check the visual bits against 0 for the\nattachment, but we haven't been doing that thusfar, and given how\nconfusingly this is specified, I can't imagine anyone relying on it.\n\nv2: Improve comments, move error condition above the\n    _mesa_get_fb0_attachment call, add forgotten \"return\"\n    (all suggested/caught by Jordan Justen).\n\nSigned-off-by: Kenneth Graunke <kenneth@whitecape.org>\nReviewed-by: Jordan Justen <jordan.l.justen@intel.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/789e0965941533b0eeb2bc822012985e7c36d9c9"},{"sha":"9184d9a0bbe8a8b88d676a20f95d66ceee9eaf21","author":{"email":"06a7711300be5898d6035f8dba5340780a12789c@free.fr","name":"Pierre Moreau"},"message":"nvc0/ir: Use double constant in handleSQRT\n\nFixes: a100d89d0998 (nv50,nvc0: Fix invalid constant.)\nSigned-off-by: Pierre Moreau <pierre.morrow@free.fr>\nReviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/9184d9a0bbe8a8b88d676a20f95d66ceee9eaf21"},{"sha":"fbe6e92899f90e7ee85420e88c807a1f2fd2be14","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"gallium: add TGSI property NEXT_SHADER\n\nRadeonsi needs to know which shader stage will execute after a shader\nin order to make the best decision about which shader variant to compile\nfirst.\n\nThis is only set for VS and TES, because we don't need it elsewhere.\n\nVS has 3 variants:\n- next shader is FS\n- next shader is GS\n- next shader is TCS\n\nTES has 2 variants:\n- next shader is FS\n- next shader is GS\n\nCurrently, radeonsi always assumes the next shader is FS, which is suboptimal,\nsince st/mesa always knows which shader is next if the GLSL program is not\na \"separate shader\".\n\nBy default, ureg always sets \"next shader is FS\".\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/fbe6e92899f90e7ee85420e88c807a1f2fd2be14"},{"sha":"2bdd7a46a92fcfa983bd53294342a0ef14098d7f","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"st/mesa: set TGSI property NEXT_SHADER\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/2bdd7a46a92fcfa983bd53294342a0ef14098d7f"},{"sha":"a73a657def40375e0c5788bd8c3db7c6b987a934","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"radeonsi: process TGSI property NEXT_SHADER\n\nThis allows compiling the main shader part as ES or LS.\n\nIf we get the correct hint, non-separable GLSL shaders no longer have to be\ncompiled as VS first, followed by LS or ES compiled on demand.\n\nThe result is that fewer shaders are compiled by piglit, but it doesn't\nimprove piglit running time.\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/a73a657def40375e0c5788bd8c3db7c6b987a934"},{"sha":"8140154ae92c6bd022e409790bb069966a857aed","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"gallium/radeon: remove old CS tracing\n\nCons:\n- it was only integrated in r600g\n- it doesn't work with GPUVM\n- it records buffer contents at the end of IBs instead of at the beginning,\n  so the replay isn't exact\n- it lacks an IB parser and user-friendliness\n\nA better solution is apitrace in combination with gallium/ddebug, which\nhas a complete IB parser and can pinpoint hanging CP packets.\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/8140154ae92c6bd022e409790bb069966a857aed"},{"sha":"20a09897a6c757a93cfb385ede7a7eb5e79cc18f","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"r600g: remove TGSI->LLVM translation\n\nIt was useful for testing and as a prototype for radeonsi bringup,\nbut it's not used anymore and doesn't support OpenGL 3.3 even.\n\nv2: try to fix OpenCL build\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>\nTested-by: Jan Vesely <jan.vesely@rutgers.edu>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/20a09897a6c757a93cfb385ede7a7eb5e79cc18f"},{"sha":"4e5dc69af158dd5eef73ad4fcd7990e49ec6ec57","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"r600g: flatten if (1) statement after removal of TGSI->LLVM\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/4e5dc69af158dd5eef73ad4fcd7990e49ec6ec57"},{"sha":"ea2bff1d115ef00aaa06797fffd4334f6a50570f","author":{"email":"8c7344a1abdb103e79ecfd488098373070c3c70e@amd.com","name":"Marek Olšák"},"message":"gallium/radeon: remove remnants of R600 TGSI->LLVM\n\nReviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/ea2bff1d115ef00aaa06797fffd4334f6a50570f"},{"sha":"6eeb284e4f74a2fe5ae6cba90f97f219935e24df","author":{"email":"bcbbb7aa705ec3a5fc5824c01a845186c3d62fca@alum.mit.edu","name":"Ilia Mirkin"},"message":"nv50/ir: normalize cube coordinates after derivatives have been computed\n\nIn \"manual\" derivative mode (always used on nv50 and sometimes on nvc0\nbut always for cube), the idea is that using the quadop instruction, we\nset up the \"other\" quads to have values such that the derivatives work\nout, and then run the texture instruction as if nothing were strange. It\npulls values from the other lanes, and does its magic.\n\nHowever cube coordinates have to be normalized - one of the 3 coords has\nto be 1, to determine which is the major axis, to say which face is\nbeing sampled. We were normalizing the coordinates first, and then\nadding the derivatives. This is wrong for two reasons:\n\n- the coordinates got normalized by a scaling factor but the\n  derivatives didn't\n- the result of the addition didn't end up normalized\n\nTo resolve this, we flip the logic around to normalize *after* the\nper-lane coordinates are set up.\n\nThis fixes a bunch of textureGrad cube dEQP tests.\n\nNOTE: nv50 cube arrays with explicit derivatives are still broken, to be\nresolved at a later date.\n\nSigned-off-by: Ilia Mirkin <imirkin@alum.mit.edu>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/6eeb284e4f74a2fe5ae6cba90f97f219935e24df"},{"sha":"adb40a739943d62508b9c79cbd85e3c67ee3b43b","author":{"email":"bcbbb7aa705ec3a5fc5824c01a845186c3d62fca@alum.mit.edu","name":"Ilia Mirkin"},"message":"st/mesa: only minify depth for 3d targets\n\nWe make sure that that image depth matches the level's depth before\ncopying it into place. However we should only be minifying the first\nlevel's depth for 3d textures - array textures have the same depth for\nall levels.\n\nThis fixes tests such as\ndEQP-GLES3.functional.texture.specification.texsubimage3d_depth.* and I\nsuspect account for a number of other odd situations I've run into where\nlevel > 0 of array textures was messed up.\n\nSigned-off-by: Ilia Mirkin <imirkin@alum.mit.edu>\nReviewed-by: Dave Airlie <airlied@redhat.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/adb40a739943d62508b9c79cbd85e3c67ee3b43b"},{"sha":"7d98bfedd73d632041d27ff12ccf7c7be74a2ddd","author":{"email":"bcbbb7aa705ec3a5fc5824c01a845186c3d62fca@alum.mit.edu","name":"Ilia Mirkin"},"message":"nv50/ir: fix indirect texturing for non-array textures on nvc0\n\nIf a layer parameter is provided, we want to flip it to position 0 (and\ncombine it with any indirect params). However if the target is not an\narray, there is no layer, so we have to shift all of the arguments down\nby one to make room for it.\n\nThis fixes situations where there were non-coordinate parameters, such\nas bias, lod, depth compare, explicit derivatives. Instead of adding a\nnew parameter at the front for the indirect reference, we would swap one\nof those in its place.\n\nFixes dEQP-GLES31.functional.shaders.opaque_type_indexing.sampler.uniform.compute.*shadow\n\nSigned-off-by: Ilia Mirkin <imirkin@alum.mit.edu>\nReported-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nTested-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/7d98bfedd73d632041d27ff12ccf7c7be74a2ddd"},{"sha":"46de6bbb775602ab237d0054e5351b0fc90d942b","author":{"email":"d6c71eaabffeede1ecc458a86a975d0b3f419fe3@amd.com","name":"Nishanth Peethambaran"},"message":"st/omx: Remove trailing spaces\n\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Nishanth Peethambaran <nishanth.peethambaran@amd.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/46de6bbb775602ab237d0054e5351b0fc90d942b"},{"sha":"eeb117a09d6c0eb2b4fa94d55e8015c8aa982727","author":{"email":"d6c71eaabffeede1ecc458a86a975d0b3f419fe3@amd.com","name":"Nishanth Peethambaran"},"message":"st/omx/dec: Correct the timestamping\n\nAttach the timestamp to the dpb buffer and use that timestamp\nwhile pushing buffer from dpb list to the omx client.\n\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Nishanth Peethambaran <nishanth.peethambaran@amd.com>\nCc: \"11.1 11.2\" <mesa-stable@lists.freedesktop.org>","distinct":false,"url":"https://api.github.com/repos/victoredwardocallaghan/mesa-GLwork/commits/eeb117a09d6c0eb2b4fa94d55e8015c8aa982727"}]}