r600g/sb: Don't read junk after EOP
Shaders that contain instruction data after an instruction with EOP could end up parsing that as an instruction, leading to various crashes and asserts in SB as it gets very confused if it sees for instance a loop start instruction jumping off to some random point. Add a couple of asserts, and print EOP bit if set in old asm printer. Signed-off-by:Glenn Kennard <glenn.kennard@gmail.com> Cc: <mesa-stable@lists.freedesktop.org> Signed-off-by:
Dave Airlie <airlied@redhat.com>
- src/gallium/drivers/r600/r600_asm.c 2 additions, 0 deletionssrc/gallium/drivers/r600/r600_asm.c
- src/gallium/drivers/r600/sb/sb_bc_decoder.cpp 1 addition, 0 deletionssrc/gallium/drivers/r600/sb/sb_bc_decoder.cpp
- src/gallium/drivers/r600/sb/sb_bc_parser.cpp 3 additions, 1 deletionsrc/gallium/drivers/r600/sb/sb_bc_parser.cpp