4 Commits

Author	SHA1	Message	Date
Chris Lattner	d2d89cbc19	Rename affineint type to index type. The name 'index' may not be perfect, but is better than the old name. Here is some justification: ... 1) affineint (as it is named) is not a type suitable for general computation (e.g. the multiply/adds in an integer matmul). It has undefined width and is undefined on overflow. They are used as the indices for forstmt because they are intended to be used as indexes inside the loop. 2) It can be used in both cfg and ml functions, and in cfg functions. As you mention, “symbols” are not affine, and we use affineint values for symbols. 3) Integers aren’t affine, the algorithms applied to them can be. :) 4) The only suitable use for affineint in MLIR is for indexes and dimension sizes (i.e. the bounds of those indexes). PiperOrigin-RevId: 216057974	2019-03-29 13:24:16 -07:00
Jacques Pienaar	775130b6b9	Add tf_control to syntax files's types. NFC ... PiperOrigin-RevId: 206587987	2019-03-29 12:48:19 -07:00
Uday Bondhugula	e990ec65d0	Internal change ... PiperOrigin-RevId: 206522239	2019-03-29 12:48:05 -07:00
James Molloy	f1c35e90c3	[mlir] Add mlir-mode.el ... PiperOrigin-RevId: 205920209	2019-03-29 12:42:34 -07:00