ttn: invalid base/range triggering nir_validate assertion
As reported in !6359 (comment 751385) the recent patchset nir: Add base/range to nir_intrinsic_load_ubo introduces a regression with some nine games that use indirect addressing. Indeed The base/range is invalid in this case (null or negative range).
The case of null range triggers a nir_validate assertion (check for negative range should probably added too).
Attached is the TGSI and nir_validate assertion of a buggy shaderbuggy_shader_compilation (with base/range generated)