tgsi: fix incorrect tgsi_shader_info::num_tokens computation
authorBrian Paul <brianp@vmware.com>
Thu, 17 May 2018 19:38:05 +0000 (13:38 -0600)
committerBrian Paul <brianp@vmware.com>
Thu, 17 May 2018 21:02:05 +0000 (15:02 -0600)
commit8fde9429c36b75d9e5afec4e221aff9b47db54f6
tree61460be7472c7682e1687d3ed3236de0cd82f6d4
parentfcba3934fc138d6b9bfa911bd6c8f1155f577b58
tgsi: fix incorrect tgsi_shader_info::num_tokens computation

We were incrementing num_tokens in each loop iteration while parsing
the shader.  But each call to tgsi_parse_token() can consume more than
one token (and often does).  Instead, just call the tgsi_num_tokens()
function.

Luckily, this issue doesn't seem to effect any current users of this
field (llvmpipe just checks for <= 1, for example).

Reviewed-by: Neha Bhende<bhenden@vmware.com>
Reviewed-by: Roland Scheidegger <sroland@vmware.com>
src/gallium/auxiliary/tgsi/tgsi_scan.c