summaryrefslogtreecommitdiffstats
path: root/mlir/utils
Commit message (Collapse)AuthorAgeFilesLines
...
* Standardize naming of statements -> instructions, revisting the code base to beChris Lattner2019-03-291-2/+2
| | | | | | | | | consistent and moving the using declarations over. Hopefully this is the last truly massive patch in this refactoring. This is step 21/n towards merging instructions and statements, NFC. PiperOrigin-RevId: 227178245
* Update vim syntax file to highlight core opsUday Bondhugula2019-03-291-0/+2
| | | | PiperOrigin-RevId: 227082502
* Rename affineint type to index type. The name 'index' may not be perfect, ↵Chris Lattner2019-03-292-3/+3
| | | | | | | | | | | | | | 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
* Add tf_control to syntax files's types. NFCJacques Pienaar2019-03-292-2/+2
| | | | PiperOrigin-RevId: 206587987
* Internal changeUday Bondhugula2019-03-291-0/+35
| | | | PiperOrigin-RevId: 206522239
* [mlir] Add mlir-mode.elJames Molloy2019-03-291-0/+68
PiperOrigin-RevId: 205920209
OpenPOWER on IntegriCloud