Re: [PATCH 0/1] MR349: vkd3d-shader/spirv: Ensure that all instructions belong to a block.

[Zebediah Figura (＠zfigura)]

> I changed it so that after `OpReturn` another dummy SPIR-V block is began and the generated SPIR-V is valid. That's a problem with the SPIR-V code generation, not with VSIR.

Shouldn't we just stop writing instructions in the current block after a jump?

-- 
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/349#note_45831