ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #zink
hikiko has joined #zink
illwieckz has joined #zink
pac85 has joined #zink
<pac85> Inside zink_gfx_program_update_optimal there ara branches that look like if (ctx->gfx_dirty) { ... } else if (ctx->dirty_gfx_stages) { ... } where the second branch is more or less just a simplified version of the one above that only handles variants. Correct? If so does it really make sense to keep the two branches after my changes?
<zmike> I'd have to check, but currently the point is to avoid unnecessary locking and hash table lookups
<pac85> I see what you mean, I'll see if I can implement this optimization in my branch
<zmike> there's a drawoverhead case for program switching, and a lot of this code has been optimized for that
<pac85> I guess I'll run that when we get closer merging to make sure there are no significant performance regressions
pac85 has quit [Quit: Konversation terminated!]
pbsds has quit [Ping timeout: 480 seconds]
illwieckz has quit [Remote host closed the connection]
illwieckz has joined #zink
pbsds has joined #zink
illwieckz has quit [Read error: Connection reset by peer]
illwieckz has joined #zink
neobrain[m] has quit []