[mlir] Fix a typo to load lsp-mode correctly.Differential Revision: https://reviews.llvm.org/D123745
[mlir] Add the Emacs support for MLIR's LSP serverIn order to use the MLIR LSP server in Emacs, first the `mlir-lsp-client.el`has to be loaded via elisp and then, one should call `lsp-mlir-setup`
[mlir] Add the Emacs support for MLIR's LSP serverIn order to use the MLIR LSP server in Emacs, first the `mlir-lsp-client.el`has to be loaded via elisp and then, one should call `lsp-mlir-setup` functionto setup the LSP client. After that simply calling the `lsp` function whilethe `mlir-mode` is active with result in finding the language server (defaultto `mlir-lsp-server`) via the `lsp-mlir-server-executable` customization variableand connecting to it by the LSP library. Users who use MLIR's language serverlibrary to create their own server can simply set the variable `lsp-mlir-server-executable`to point to their own implementation executable.Reviewed By: tschuettDifferential Revision: https://reviews.llvm.org/D123002
show more ...
Update header notices.PiperOrigin-RevId: 240457737
Automated rollback of changelist 232728977.PiperOrigin-RevId: 232944889
Automated rollback of changelist 232717775.PiperOrigin-RevId: 232807986
Rename the 'if' operation in the AffineOps dialect to 'affine.if' and namespacethe AffineOps dialect with 'affine'.PiperOrigin-RevId: 232728977
NFC: Rename the 'for' operation in the AffineOps dialect to 'affine.for'. The is the second step to adding a namespace to the AffineOps dialect.PiperOrigin-RevId: 232717775
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 gene
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
Add tf_control to syntax files's types. NFCPiperOrigin-RevId: 206587987
[mlir] Add mlir-mode.elPiperOrigin-RevId: 205920209