i965: Don't treat HW_REGs as barriers if they're immediates.
authorMatt Turner <mattst88@gmail.com>
Thu, 17 Apr 2014 20:55:06 +0000 (13:55 -0700)
committerMatt Turner <mattst88@gmail.com>
Mon, 26 May 2014 03:16:46 +0000 (20:16 -0700)
commit6148e94e26ff4b6cbba452121c76d564f25f194d
tree4632e5fbd3456798df315d7aa5366e8cf04a4b43
parentc938be8ad272a06bc0e91c4e718b61a0c5de400e
i965: Don't treat HW_REGs as barriers if they're immediates.

We had a handful of cases where we'd used brw_imm_*() to generate an
immediate, rather than fs_reg(). We shouldn't do that but we shouldn't
limit scheduling flexibility on account of immediate arguments either.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
src/mesa/drivers/dri/i965/brw_schedule_instructions.cpp