From 472ef2f98d32c931a15495a344371ea60a6b633e Mon Sep 17 00:00:00 2001 From: Jason Ekstrand Date: Tue, 7 May 2019 20:11:08 -0500 Subject: [PATCH] intel/fs/ra: Initialize grf_used with first_non_payload_grf There's no reason why we need to use the calculated payload_node_count value which is just first_non_payload_grf aligned up. The grf_used value will be aligned up to 16 anyway (which is a much bigger alignment) before being handed off to hardware. Reviewed-by: Kenneth Graunke --- src/intel/compiler/brw_fs_reg_allocate.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/intel/compiler/brw_fs_reg_allocate.cpp b/src/intel/compiler/brw_fs_reg_allocate.cpp index 35903c4030e..2debd36f231 100644 --- a/src/intel/compiler/brw_fs_reg_allocate.cpp +++ b/src/intel/compiler/brw_fs_reg_allocate.cpp @@ -749,7 +749,7 @@ fs_visitor::assign_regs(bool allow_spilling, bool spill_all) * regs in the register classes back down to real hardware reg * numbers. */ - this->grf_used = payload_node_count; + this->grf_used = this->first_non_payload_grf; for (unsigned i = 0; i < this->alloc.count; i++) { int reg = ra_get_node_reg(g, i); -- 2.30.2