When doing RA we end up with adding ValueDef references to Values across
all over the shader. This is all fine until we remove the Instruction
defining those Values, which happens when spilling values.
Instead of manipulating the values directly we should just track all
merged in defs in a
I will touch them in the next commit
Signed-off-by: Karol Herbst
---
.../drivers/nouveau/codegen/nv50_ir_ra.cpp| 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp
Change of plan, I am going to do 20.0, but I'm hoping I can find someone to
hand off 19.3 to while I do it, because managing two branches at the same time
is really draining.
I'll open an MR, let's plan for the branchpoint/-rc1 on January 29th as Samuel
suggests.
On Wed, Jan 15, 2020, at
I should have said that in my previous reply:
We would like to have ACO/GFX6 support and
VK_AMD_shader_explicit_vertex_parameter in Mesa 20.0.
I think it's doable if branchpoint is in two weeks or something like that.
FWIW, 19.0 branchpoint was on January 29 last year.
On 1/15/20 5:50 PM,
I believe Juan is supposed to be making the 20.0 release.
Dylan
Quoting Jason Ekstrand (2020-01-15 08:13:38)
> When were we planning to cut the 20.0 release? We just landed Vulkan 1.2
> support for ANV and RADV this morning so it seems like a good time to me. The
> release calendar has nothing
If we can wait end of january that would be highly appreciated :-)
On 1/15/20 5:13 PM, Jason Ekstrand wrote:
When were we planning to cut the 20.0 release? We just landed Vulkan
1.2 support for ANV and RADV this morning so it seems like a good time
to me. The release calendar has nothing for
When were we planning to cut the 20.0 release? We just landed Vulkan 1.2
support for ANV and RADV this morning so it seems like a good time to me.
The release calendar has nothing for 2020:
https://www.mesa3d.org/release-calendar.html
--Jason
___
