| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
mlir/LogicalResult: move into llvm (#97309) This patch is part of a project to move the Presburger library into LLVM. | 2 年前 | |
[MLIR][parser] Add token type and parser methods for forward slashes (#125056) This adds a token for a forward slash to the token definition list and the methods to AsmParser::parseSlash() and AsmParser::parseOptionalSlash(), similar to other tokens used as operators (e.g., star, plus, etc.). This allows implementations of attributes that contain arithmetic expressions to support operators with a forward slash, e.g., a division. The newly added check tests trigger the parsing of a slash in an attribute. | 1 年前 | |
[MLIR][NFC] Fix incomplete boundary comments. (#133516) I observed that we have the boundary comments in the codebase like: //===----------------------------------------------------------------------===// // ... //===----------------------------------------------------------------------===// I also observed that there are incomplete boundary comments. The revision is generated by a script that completes the boundary comments. //===----------------------------------------------------------------------===// // ... ... Signed-off-by: hanhanW <hanhan0912@gmail.com> | 1 年前 | |
[mlir] Use a new constructor of ArrayRef (NFC) (#146009) ArrayRef now has a new constructor that takes a parameter whose type has data() and size(). This patch migrates: ArrayRef<T>(X.data(), X.size() to: ArrayRef<T>(X) | 1 年前 | |
[mlir] Refactor the Parser library in preparation for an MLIR binary format The current Parser library is solely focused on providing API for the textual MLIR format, but MLIR will soon also provide a binary format. This commit renames the current Parser library to AsmParser to better correspond to what the library is actually intended for. A new Parser library is added which will act as a unified parser interface between both text and binary formats. Most parser clients are unaffected, given that the unified interface is essentially the same as the current interface. Only clients that rely on utilizing the AsmParserState, or those that want to parse Attributes/Types need to be updated to point to the AsmParser library. Differential Revision: https://reviews.llvm.org/D129605 | 3 年前 | |
| 11 个月前 | ||
[mlir] Make parser not rely on terminating null. (#151007) Used in follow up to parse slices of buffer. | 1 年前 | |
[mlir] Make parser not rely on terminating null. (#151007) Used in follow up to parse slices of buffer. | 1 年前 | |
[mlir] Add FileRange location type. (#80213) This location type represents a contiguous range inside a file. It is effectively a pair of FileLineCols. Add new type and make FileLineCol a view for case where it matches existing previous one. The location includes filename and optional start line & col, and end line & col. Considered common cases are file:line, file:line:col, file:line:start_col to file:line:end_col and general range within same file. In memory its encoded as trailing objects. This keeps the memory requirement the same as FileLineColLoc today (makes the rather common File:Line cheaper) at the expense of extra work at decoding time. Kept the unsigned type. There was the option to always have file range be castable to FileLineColLoc. This cast would just drop other fields. That may result in some simpler staging. TBD. This is a rather minimal change, it does not yet add bindings (C or Python), lowering to LLVM debug locations etc. that supports end line:cols. --------- Co-authored-by: River Riddle <riddleriver@gmail.com> | 1 年前 | |
[mlir] Migrate away from a soft-deprecated constructor of APInt (NFC) (#166128) We have: /// Once all uses of this constructor are migrated to other constructors, /// consider marking this overload ""= delete" to prevent calls from being /// incorrectly bound to the APInt(unsigned, uint64_t, bool) constructor. LLVM_ABI APInt(unsigned numBits, unsigned numWords, const uint64_t bigVal[]); This patch migrates away from this soft-deprecated constructor. | 9 个月前 | |
[MLIR] Imporve location tracking for parseElementsLiteralType (#127992) This commit improves line location tracking in case of error reporting to the user in parseElementsLiteralType. There are two cases: the type is already parsed [1] or not yet parsed [2]. With these changes we print the error at the attribute's location in both cases to ensure consistency. Case 1) mlir memref<i32> = dense<[3]> ^ Case 2) mlir dense<[3]> : memref<i32> ^ Note that today for a simple: mlir func.func @main() { %0 = arith.constant dense<[3]> : i32 return } we print the error after the constant: ./bin/c.mlir:3:3: error: elements literal must be a shaped type return ^ | 1 年前 | |
| 11 个月前 | ||
[MLIR] Apply clang-tidy fixes for misc-include-cleaner (NFC) | 2 年前 | |
[mlir] Remove remaining uses of llvm::Optional (NFC) This patch removes one "using" declaration and #include "llvm/ADT/Optional.h". It keeps several "using" declarations in headers for downstream users. This is part of an effort to migrate from llvm::Optional to std::optional: https://discourse.llvm.org/t/deprecating-llvm-optional-x-hasvalue-getvalue-getvalueor/63716 | 3 年前 | |
[MLIR][parser] Add token type and parser methods for forward slashes (#125056) This adds a token for a forward slash to the token definition list and the methods to AsmParser::parseSlash() and AsmParser::parseOptionalSlash(), similar to other tokens used as operators (e.g., star, plus, etc.). This allows implementations of attributes that contain arithmetic expressions to support operators with a forward slash, e.g., a division. The newly added check tests trigger the parsing of a slash in an attribute. | 1 年前 | |
[mlir] Remove unused includes (NFC) (#150476) These are identified by misc-include-cleaner. I've filtered out those that break builds. Also, I'm staying away from llvm-config.h, config.h, and Compiler.h, which likely cause platform- or compiler-specific build failures. | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 1 年前 |