Stanislav Mekhanoshin 563a9ce27a [TBLGEN] Fix subreg value overflow in DAGISelMatcher ... Tablegen's DAGISelMatcher emits integers in a VBR format, so if an integer is below 128 it can fit into a single byte, otherwise high bit is set, next byte is used etc. MatcherTable is essentially an unsigned char table. When SelectionDAGISel parses the table it does a reverse translation. In a situation when numeric value of an integer to emit is unknown it can be emitted not as OPC_EmitInteger but as OPC_EmitStringInteger using a symbolic name of the value. In this situation the value should not exceed 127. One of the situations when OPC_EmitStringInteger is used is if we need to emit a subreg into a matcher table. However, number of subregs can exceed 127. Currently last defined subreg for AMDGPU is 192. That results in a silent bug in the ISel with matcher reading from an invalid offset. Fixed this bug to emit actual VBR encoded value for a subregs which value exceeds 127. Differential Revision: https://reviews.llvm.org/D74368		2020-02-12 13:29:57 -08:00
..
GlobalISelEmitterCommon.td	TableGen/GlobalISel: Fix pattern matching of immarg literals	2020-01-09 17:37:52 -05:00
reg-with-subregs-common.td	[TBLGEN] Fix subreg value overflow in DAGISelMatcher	2020-02-12 13:29:57 -08:00