URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=838baab47263389704c0e5bd635447f9ac3439c3
Author: Dylan Baker <[email protected]>
Date: Wed Feb 13 09:11:02 2019 -0800
version: bump for 19.0-rc4
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d8534f931c22463b1fab20248c114d1feea2a48b
Author: Juan A. Suarez Romero <[email protected]>
Date: Tue Feb 12 19:19:13 2019 +0100
anv/cmd_buffer: check for NULL framebuffer
This can happen when we record a VkCmdDraw in a secondary buffer that
was created inheriting from the primary buffer, but with the framebuffer
set to NULL in the VkCommandBufferInheritanceInfo.
Vulkan 1.1.81 spec says that "the application must ensure (using scissor
if neccesary) that all rendering is contained in the render area [...]
[which] must be contained within the framebuffer dimesions".
While this should be done by the application, commit 465e5a86 added the
clamp to the framebuffer size, in case of application does not do it.
But this requires to know the framebuffer dimensions.
If we do not have a framebuffer at that moment, the best compromise we
can do is to just apply the scissor as it is, and let the application to
ensure the rendering is contained in the render area.
v2: do not clamp to framebuffer if there isn't a framebuffer
v3 (Jason):
- clamp earlier in the conditional
- clamp to render area if command buffer is primary
v4: clamp also x and y to render area (Jason)
v5: rename used variables (Jason)
Fixes: 465e5a86 ("anv: Clamp scissors to the framebuffer boundary")
CC: Jason Ekstrand <[email protected]>
Reviewed-by: Jason Ekstrand <[email protected]>
(cherry picked from commit 1ad26f941792f07f226c054811be78b0c0ac9fce)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=1f33f3cf3a4441d76708b18d124477f099c0d491
Author: Samuel Pitoiset <[email protected]>
Date: Tue Feb 12 09:01:50 2019 +0100
radv: fix using LOAD_CONTEXT_REG with old GFX ME firmwares on GFX8
This fixes a critical issue.
Cc: <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109575
Signed-off-by: Samuel Pitoiset <[email protected]>
Reviewed-by: Bas Nieuwenhuizen <[email protected]>
(cherry picked from commit 1b8983c25be19073c02fe9630e949be55f8280fa)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=fbcd1ad42cf0ea64b08045d4d9fc932ea1073a8b
Author: Samuel Pitoiset <[email protected]>
Date: Mon Feb 11 10:17:52 2019 +0100
radv: fix compiler issues with GCC 9
"The C standard says that compound literals which occur inside of
the body of a function have automatic storage duration associated
with the enclosing block. Older GCC releases were putting such
compound literals into the scope of the whole function, so their
lifetime actually ended at the end of containing function. This
has been fixed in GCC 9. Code that relied on this extended lifetime
needs to be fixed, move the compound literals to whatever scope
they need to accessible in."
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109543
Cc: <[email protected]>
Signed-off-by: Samuel Pitoiset <[email protected]>
Reviewed-by: Gustaw Smolarczyk <[email protected]>
Reviewed-by: Bas Nieuwenhuizen <[email protected]>
(cherry picked from commit 129a9f4937b8f2adb4d37999677d748d816d611c)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=9a5c8d2aab26eec839a554cc199798c61ca54788
Author: Kenneth Graunke <[email protected]>
Date: Sun Feb 10 22:49:20 2019 -0800
st/mesa: Limit GL_MAX_[NATIVE_]PROGRAM_PARAMETERS_ARB to 2048
Piglit's vp-max-array test creates a vertex program containing a uniform
array sized to the value of GL_MAX_NATIVE_PROGRAM_PARAMETERS_ARB. Mesa
will then add additional state-var parameters for things like the MVP
matrix.
radeonsi currently exposes a value of 4096, derived from constant buffer
upload size. This means the array will have 4096 elements, and the
extra MVP state-vars would get a prog_src_register::Index of over 4096.
Unfortunately, prog_src_register::Index is a signed 13-bit integer, so
values beyond 4096 end up turning into negative numbers. Negative
source indexes are only valid for relative addressing, so this ends up
generating illegal IR.
In prog_to_nir, this would cause an out of bounds array access.
st_mesa_to_tgsi checks for a negative value, assumes it's bogus,
and remaps it to parameter 0 in order to get something in-range.
This isn't right - instead of reading the MVP matrix, it would read
the first element of the vertex program's large array. But the test
only checks that the program compiles, so we never noticed that it
was broken.
This patch limits the size of the program limits, with the understanding
that we may need to generate additional state-vars internally. i965 has
exposed 1024 for this limit for years, so I don't expect lowering it to
2048 will cause any practical problems for radeonsi or other drivers.
Fixes vp-max-array with prog_to_nir.c.
Cc: "19.0" <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
(cherry picked from commit f45dd6d31b2ff46a082931386ccd0bf043cfad59)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=c55008e5a04e91ea03b2047c68121ee009704366
Author: Leo Liu <[email protected]>
Date: Fri Feb 8 09:48:23 2019 -0500
st/va/vp9: set max reference as default of VP9 reference number
If there is no information about number of render targets
Signed-off-by: Leo Liu <[email protected]>
Reviewed-by: Boyuan Zhang <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit a0a52a036708dbf5989778795fd67a79e3226289)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=ab585817e6a34893674b65aba77252d7bff43cc5
Author: Leo Liu <[email protected]>
Date: Fri Feb 8 08:56:53 2019 -0500
st/va: fix the incorrect max profiles report
Add "PIPE_VIDEO_PROFILE_MAX" to enum, so it will make sure here will
be correct when adding more profiles in the future.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109107
Signed-off-by: Leo Liu <[email protected]>
Reviewed-by: Boyuan Zhang <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 21cdb828a3f4d1e2f140fc7c81a4bc305b2f6b04)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=75bec50c2a3cba0bb1dd2ac18599d94e81422609
Author: Marek Olšák <[email protected]>
Date: Mon Feb 4 15:12:17 2019 -0500
winsys/amdgpu: don't drop manually added fence dependencies
wow, it's hard to believe that fence and syncobjs dependencies were ignored.
Cc: 18.3 19.0 <[email protected]>
Reviewed-by: Nicolai Hähnle <[email protected]>
(cherry picked from commit ddfe209a0d61917e7b08100eeac82f4c20ca59e8)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=62b3bd8cd1dfe95a0d7a874a7df25aa09215999a
Author: Marek Olšák <[email protected]>
Date: Fri Feb 1 17:10:46 2019 -0500
radeonsi: fix EXPLICIT_FLUSH for flush offsets > 0
Cc: 18.3 19.0 <[email protected]>
Reviewed-by: Nicolai Hähnle <[email protected]>
(cherry picked from commit 61c678d4bc91d2ff9ca8c9b183e08daf07d8d24c)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=fb3485bc9248a12f47b07b593f0a81d58cbb3155
Author: Marek Olšák <[email protected]>
Date: Fri Feb 1 17:10:46 2019 -0500
gallium/u_threaded: fix EXPLICIT_FLUSH for flush offsets > 0
Cc: 18.3 19.0 <[email protected]>
Reviewed-by: Nicolai Hähnle <[email protected]>
(cherry picked from commit 4522f01d4ef9e8a1bb945ca28fba7649aae2171b)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=2a97a3a8e708ec104c7ac18fff7c518be7487900
Author: Ilia Mirkin <[email protected]>
Date: Sat Feb 9 22:36:49 2019 -0500
nvc0: we have 16k-sized framebuffers, fix default scissors
For some reason we don't use view volume clipping by default, and use
scissors instead. These scissors were set to an 8k max fb size, while
the driver advertises 16k-sized framebuffers.
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: <[email protected]>
(cherry picked from commit cc79a1483ffb7b91edc97c9870eadcab1e83b8f3)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=ab70eccc75ecf90f82d5e69c4db39226774ddfa5
Author: Karol Herbst <[email protected]>
Date: Wed Jan 16 15:17:31 2019 +0100
st/mesa: require RGBA2, RGB4, and RGBA4 to be renderable
If the driver does not support rendering to these formats but does
support texturing, we can end up in incompatibilities between textures
and renderbuffers that are then copied to.
Fixes KHR-GL45.copy_image.functional on nvc0
Reviewed-by: Ilia Mirkin <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit cbd1ad6165f0aea7fb7c6fd1b36ad5317dd65cb7)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=24bb2771b648340011ec3913bf15b2785c4c2ee2
Author: Karol Herbst <[email protected]>
Date: Fri Aug 25 19:22:03 2017 +0200
gallium: add PIPE_CAP_MAX_VARYINGS
Some NVIDIA hardware can accept 128 fragment shader input components,
but only have up to 124 varying-interpolated input components. We add a
new cap to express this cleanly. For most drivers, this will have the
same value as PIPE_SHADER_CAP_MAX_INPUTS for the fragment shader.
Fixes KHR-GL45.limits.max_fragment_input_components
Conflicts resolved by Dylan
Signed-off-by: Karol Herbst <[email protected]>
[imirkin: rebased, improved docs/commit message]
Signed-off-by: Ilia Mirkin <[email protected]>
Acked-by: Rob Clark <[email protected]>
Acked-by: Eric Anholt <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 6010d7b8e8bee1bcea2b329cf6d3b44c5fc3ca66)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=7b5e0f8316e7294617887e8df072f6b8009b849a
Author: Karol Herbst <[email protected]>
Date: Sun Jul 1 09:44:48 2018 +0200
gm107/ir: add fp64 rsq
Acked-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit cce495572136a606dd2a35e79f45080c3796e2cc)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=77102d015147b4a2495d0dec52d4e395af710aad
Author: Karol Herbst <[email protected]>
Date: Sat Jun 30 23:09:27 2018 +0200
gm107/ir: add fp64 rcp
Acked-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 815a8e59c6d462a7008653ea9e3010d40b6ba589)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=c96d4331051388fa489f486d53c06200b8aee7cf
Author: Karol Herbst <[email protected]>
Date: Mon Aug 14 23:55:25 2017 +0200
gk104/ir: Use the new rcp/rsq in library
[imirkin: add a few more "long" prefixes to safen things up]
Acked-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 12669d29705a26478aa691cb454149628be65f17)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=81810fa5db5e86e510a55f9c69b8d7759124b098
Author: Boyan Ding <[email protected]>
Date: Thu Mar 9 13:55:19 2017 +0800
gk110/ir: Use the new rcp/rsq in library
v2: (Karol Herbst <[email protected]>
* fix Value setup for the builtins
Signed-off-by: Boyan Ding <[email protected]>
[imirkin: track the fp64 flag when switching ops to calls]
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 656ad060518d067a3b311db8c2de2a396fb41898)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=c5b9774eb468fa772681807a4c939275937ca560
Author: Boyan Ding <[email protected]>
Date: Thu Mar 9 13:55:18 2017 +0800
gk110/ir: Add rsq f64 implementation
Signed-off-by: Boyan Ding <[email protected]>
Acked-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 7937408052a1896f0b08b0110bb8a1790eeee351)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a08aba86da19f1ab642272fb517a28919e482536
Author: Boyan Ding <[email protected]>
Date: Thu Mar 9 13:55:17 2017 +0800
gk110/ir: Add rcp f64 implementation
Signed-off-by: Boyan Ding <[email protected]>
Acked-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 04593d9a73ea257a36cc3b9fb5cd41427beaaea5)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d278b3c187d426fea5ded7e8d97022efc9e9d7e3
Author: Ilia Mirkin <[email protected]>
Date: Tue Feb 5 03:05:33 2019 -0500
nvc0: stick zero values for the compute invocation counts
Not quite perfect, but at least we don't end up with random values in
the query buffer.
Fixes
KHR-GL45.pipeline_statistics_query_tests_ARB.functional_default_qo_values
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 6adb9b38bfb1f6ee4c94596bf0744225aa8e967a)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=5a9b7bce9cee5563e94e75c93fffe462405dfcb1
Author: Ilia Mirkin <[email protected]>
Date: Mon Feb 4 22:57:06 2019 -0500
nv50,nvc0: use condition for occlusion queries when already complete
For the NO_WAIT variants, we would jump into the ALWAYS case for both
nested and inverted occlusion queries. However if the query had
previously completed, the application could reasonably expect that the
render condition would follow that result.
To resolve this, we remove the nesting distinction which unnecessarily
created an imbalance between the regular and inverted cases (since
there's no "zero" condition mode). We also use the proper comparison if
we know that the query has completed (which could happen as a result of
an earlier get_query_result call).
Fixes KHR-GL45.conditional_render_inverted.functional
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit e00799d3dc0595dc3998dbf199ceec8b1eece966)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=b9e5e15f877beb63af7020e145791cdbd77d9de9
Author: Ilia Mirkin <[email protected]>
Date: Sun Feb 3 21:55:12 2019 -0500
nvc0: fix 3d images on kepler
Looks like SUBFM.3D and SUEAU are perfectly capable of dealing with 3d
tiling, they just need the correct inputs. Supply them.
We also have to deal with the case where a 2d "layer" of a 3d image is
bound. In this case, we supply the z coordinate separately to the
shader, which has to optionally treat every 2d case as if it could be a
slice of a 3d texture.
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 162352e6711b3ceab114686f7a3248074339e7f7)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=f305135e0bde236d3e76a1aaff1279890dbb595a
Author: Ilia Mirkin <[email protected]>
Date: Sun Feb 3 10:06:24 2019 -0500
nvc0/ir: always use CG mode for loads from atomic-only buffers
Atomic operations don't update the local cache, which means that we
would have to issue CCTL operations in order to get the updated values.
When we know that a buffer is primarily used for atomic operations, it's
easier to just avoid the caching at that level entirely.
The same issue persists for non-atomic buffers, which will have to be
fixed separately.
Fixes the failing dEQP-GLES31.functional.atomic_counter.* tests.
Signed-off-by: Ilia Mirkin <[email protected]>
Reviewed-by: Karol Herbst <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 4443b6ddf2e08d06f3d0457cf20a2e04244cde37)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=eb766a259e18cd40e03d8e998e4cf088c0a36615
Author: Ilia Mirkin <[email protected]>
Date: Sat Feb 2 16:23:50 2019 -0500
nvc0: add support for handling indirect draws with attrib conversion
The hardware does not natively support FIXED and DOUBLE formats. If
those are used in an indirect draw, they have to be converted. Our
conversion tries to be clever about only converting the data that's
needed. However for indirect, that won't work.
Given that DOUBLE or FIXED are highly unlikely to ever be used with
indirect draws, read the indirect buffer on the CPU and issue draws
directly.
Fixes the failing dEQP-GLES31.functional.draw_indirect.random.* tests.
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 399215eb7a0517463e5757c598d6cff6ae2301d0)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a1ae60e9a30ec315323f3c770b8e53161ad98738
Author: Bas Nieuwenhuizen <[email protected]>
Date: Wed Jan 23 22:44:05 2019 +0100
amd/common: Use correct writemask for shared memory stores.
The check was for 1 bit being set, which is clearly not what we want.
CC: <[email protected]>
Reviewed-by: Samuel Pitoiset <[email protected]>
(cherry picked from commit 3c24fc64c7a4e564d84843fab7db25963d574d99)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=37ade3a566585df82abeb3bcf661624b695b79ac
Author: Bas Nieuwenhuizen <[email protected]>
Date: Tue Jan 22 22:29:26 2019 +0100
radv: Only look at pImmutableSamples if the descriptor has a sampler.
Equivalent of ANV patch c7f4a2867ce492d78c1f8e2870c0a593d280572d
CC: <[email protected]>
Reviewed-by: Samuel Pitoiset <[email protected]>
(cherry picked from commit 39ab4e12f71a640b43403a110d3d85565b59d16c)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=92fa6d695935e9755e6f5cdf00138750cf164aa7
Author: Bart Oldeman <[email protected]>
Date: Sun Feb 3 02:57:10 2019 +0000
gallium-xlib: query MIT-SHM before using it.
When Mesa is compiled for gallium-xlib using e.g.
./configure --enable-glx=gallium-xlib --disable-dri --disable-gbm
-disable-egl
and is used by an X server (usually remotely via SSH X11 forwarding)
that does not support MIT-SHM such as XMing or MobaXterm, OpenGL
clients report error messages such as
Xlib: extension "MIT-SHM" missing on display "localhost:11.0".
ad infinitum.
The reason is that the code in src/gallium/winsys/sw/xlib uses
MIT-SHM without checking for its existence, unlike the code
in src/glx/drisw_glx.c and src/mesa/drivers/x11/xm_api.c.
I copied the same check using XQueryExtension, and tested with
glxgears on MobaXterm.
This issue was reported before here:
https://lists.freedesktop.org/archives/mesa-users/2016-July/001183.html
Reviewed-by: Eric Anholt <[email protected]>
Reviewed-by: Emil Velikov <[email protected]>
Cc: <[email protected]>
(cherry picked from commit a203eaa4f4fb672b95426289b8dad3a8998f92d7)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=5e85df1cfd53811149c99be446a1e8e103f377fa
Author: Ilia Mirkin <[email protected]>
Date: Mon Feb 4 23:33:09 2019 -0500
nv50,nvc0: add explicit settings for recent caps
Signed-off-by: Ilia Mirkin <[email protected]>
Cc: 19.0 <[email protected]>
(cherry picked from commit 38f542783faa360020b77fdd76b97f207a9e0068)
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e9dc4e252f85e84038639f9e080e72e1effb50db
Author: Marek Olšák <[email protected]>
Date: Wed Jan 23 19:48:26 2019 -0500
meson: drop the xcb-xrandr version requirement
autotools doesn't have any requirement. This fixes meson on Ubuntu 16.04.
Cc: 18.3 19.0 <[email protected]>
Reviewed-by: Erik Faye-Lund <[email protected]>
(cherry picked from commit 1e85cfb91a08565f28f51cc19573324722765823)
_______________________________________________
mesa-commit mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-commit
