| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[MLIR] Split ExecutionEngine Initialization out of ctor into an explicit method call (#153524) Retry landing https://github.com/llvm/llvm-project/pull/153373 ## Major changes from previous attempt - remove the test in CAPI because no existing tests in CAPI deal with sanitizer exemptions - update mlir/docs/Dialects/GPU.md to reflect the new behavior: load GPU binary in global ctors, instead of loading them at call site. - skip the test on Aarch64 since we have an issue with initialization there --------- Co-authored-by: Mehdi Amini <joker.eph@gmail.com> | 11 个月前 | |
| 11 个月前 | ||
[MLIR] Split ExecutionEngine Initialization out of ctor into an explicit method call (#153524) Retry landing https://github.com/llvm/llvm-project/pull/153373 ## Major changes from previous attempt - remove the test in CAPI because no existing tests in CAPI deal with sanitizer exemptions - update mlir/docs/Dialects/GPU.md to reflect the new behavior: load GPU binary in global ctors, instead of loading them at call site. - skip the test on Aarch64 since we have an issue with initialization there --------- Co-authored-by: Mehdi Amini <joker.eph@gmail.com> | 11 个月前 | |
[mlir][python] bind block predecessors and successors (#145116) bind block.getSuccessor and block.getPredecessors. | 1 年前 | |
[mlir][irdl] Introduce names in IRDL value lists (#123525) In order to meaningfully generate getters and setters from IRDL, it makes sense to embed the names of operands, results, etc. in the IR definition. This PR introduces this feature. Names are constrained similarly to TableGen names. | 1 年前 | |
[NFC][Py Reformat] Reformat python files in mlir subdir This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with black. If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run git checkout --ours <yourfile> and then reformat it with black. If you run into any problems, post to discourse about it and we will try to help. RFC Thread below: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Differential Revision: https://reviews.llvm.org/D150782 | 3 年前 | |
[mlir] Add splitDebugFilename field in DIComplileUnitAttr. (#160704) Mostly mechanical changes to add the missing field. | 10 个月前 | |
| 1 年前 | ||
Fix tsan problem where the per-thread shared_ptr() can be locked right before the cache is destroyed causing a race where it tries to remove an entry from a destroyed cache. This is a rollforward with fixes of https://reviews.llvm.org/rGbcc10817d5569172ee065015747e226280e9b698 (originally https://reviews.llvm.org/D142394). The original patch exposed an asan problem on aarch64, which is fixed by simply calling the context destructors properly. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D143294 | 3 年前 | |
Fix printing of mlirUniformQuantizedSubChannelTypeGetNumBlockSizes in 32-bit machine. (#133763) Fixes the issue reported in https://github.com/llvm/llvm-project/pull/120172#issuecomment-2763212827 cc @mgorny | 1 年前 | |
[mlir] Fix unused-variable warning w/o assertions. (#99489) | 2 年前 | |
[mlir][SMT] add python bindings (#135674) This PR adds "rich" python bindings to SMT dialect. | 1 年前 | |
[mlir][sparse] Enable explicit and implicit value in sparse encoding (#88975) 1. Explicit value means the non-zero value in a sparse tensor. If explicitVal is set, then all the non-zero values in the tensor have the same explicit value. The default value Attribute() indicates that it is not set. 2. Implicit value means the "zero" value in a sparse tensor. If implicitVal is set, then the "zero" value in the tensor is equal to the implicit value. For now, we only support 0 as the implicit value but it could be extended in the future. The default value Attribute() indicates that the implicit value is 0 (same type as the tensor element type). Example: #CSR = #sparse_tensor.encoding<{ map = (d0, d1) -> (d0 : dense, d1 : compressed), posWidth = 64, crdWidth = 64, explicitVal = 1 : i64, implicitVal = 0 : i64 }> Note: this PR tests that implicitVal could be set to other values as well. The following PR will add verifier and reject any value that's not zero for implicitVal. | 2 年前 | |
Fix tsan problem where the per-thread shared_ptr() can be locked right before the cache is destroyed causing a race where it tries to remove an entry from a destroyed cache. This is a rollforward with fixes of https://reviews.llvm.org/rGbcc10817d5569172ee065015747e226280e9b698 (originally https://reviews.llvm.org/D142394). The original patch exposed an asan problem on aarch64, which is fixed by simply calling the context destructors properly. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D143294 | 3 年前 | |
[mlir] Fix warning due to non ISO standard __FUNCTION__ usage (#91851) This PR fixes the warning message due to the non ISO standard usage of __FUNCTION__ /home/lewuathe/llvm-project/mlir/test/CAPI/transform_interpreter.c: In function ‘testApplyNamedSequence’: /home/lewuathe/llvm-project/mlir/test/CAPI/transform_interpreter.c:21:27: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic] 21 | fprintf(stderr, "%s\n", __FUNCTION__); | As __FUNCTION__ is another name of __func__ and it conforms to the specification. We should be able to use __func__ here. Ref: https://stackoverflow.com/questions/52962812/how-to-silence-gcc-pedantic-wpedantic-warning-regarding-function Compiler Ubuntu clang version 18.1.3 (1) Target: x86_64-pc-linux-gnu | 2 年前 | |
[mlir][llvmir][reland] expose Type(To/From)LLVMIRTranslator C API (#125110) | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 11 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 1 年前 |