#
db791b27 |
| 02-Jul-2024 |
Ramkumar Ramachandra <ramkumar.ramachandra@codasip.com> |
mlir/LogicalResult: move into llvm (#97309)
This patch is part of a project to move the Presburger library into
LLVM.
|
#
516ccce7 |
| 14-Mar-2024 |
Ingo Müller <ingomueller@google.com> |
[mlir] Make the split markers of splitAndProcessBuffer configurable. (#84765)
This allows to define custom splitters, which is interesting for
non-MLIR inputs and outputs to `mlir-translate`. For e
[mlir] Make the split markers of splitAndProcessBuffer configurable. (#84765)
This allows to define custom splitters, which is interesting for
non-MLIR inputs and outputs to `mlir-translate`. For example, one may
use `; -----` as a splitter of `.ll` files. The splitters are now passed
as arguments into `splitAndProcessBuffer`, the input splitter defaulting
to the previous default (`// -----`) and the output splitter defaulting
to the empty string, which also corresponds to the previous default. The
behavior of the input split marker should not change at all; however,
outputs now have one new line *more* than before if there is no splitter
(old: `insertMarkerInOutput = false`, new: `outputSplitMarker = ""`) and
one new line *less* if there is one. The value of the input splitter is
exposed as a command line options of `mlir-translate` and other tools as
an optional value to the previously existing flag `-split-input-file`,
which defaults to the default splitter if not specified; the value of
the output splitter is exposed with the new `-output-split-marker`,
which default to the empty string in `mlir-translate` and the default
splitter in the other tools. In short, the previous usage or omission of
the flags should result in previous behavior (modulo the new lines
mentioned before).
show more ...
|
#
88d319a2 |
| 14-Dec-2023 |
Kazu Hirata <kazu@google.com> |
[mlir] Use StringRef::{starts,ends}_with (NFC)
This patch replaces uses of StringRef::{starts,ends}with with StringRef::{starts,ends}_with for consistency with std::{string,string_view}::{starts,end
[mlir] Use StringRef::{starts,ends}_with (NFC)
This patch replaces uses of StringRef::{starts,ends}with with StringRef::{starts,ends}_with for consistency with std::{string,string_view}::{starts,ends}_with in C++20.
I'm planning to deprecate and eventually remove StringRef::{starts,ends}with.
show more ...
|
#
9560f021 |
| 28-Jun-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir] Add `enableSplitting` and `insertMarkerInOutput` options to `splitAndProcessBuffer`
`enableSplitting` simply enables/disables whether we should split or use the full buffer. `insertMarkerInOu
[mlir] Add `enableSplitting` and `insertMarkerInOutput` options to `splitAndProcessBuffer`
`enableSplitting` simply enables/disables whether we should split or use the full buffer. `insertMarkerInOutput` toggles if split markers should be inserted in between prcessed output chunks.
These options allow for merging the duplicate code paths we have when splitting is optional.
Differential Revision: https://reviews.llvm.org/D128764
show more ...
|
#
6842ec42 |
| 26-Jan-2022 |
River Riddle <riddleriver@gmail.com> |
[mlir][NFC] Add a using for llvm::SMLoc/llvm::SMRange to LLVM.h
These are used pervasively during parsing.
Differential Revision: https://reviews.llvm.org/D118291
|
#
efb7727a |
| 12-Dec-2021 |
Jacques Pienaar <jpienaar@google.com> |
[mlir] Flag near misses in file splitting
Flags some potential cases where splitting isn't happening and so could result in confusing results. Also update some test files where there were near misse
[mlir] Flag near misses in file splitting
Flags some potential cases where splitting isn't happening and so could result in confusing results. Also update some test files where there were near misses in splitting that seemed unintentional.
Differential Revision: https://reviews.llvm.org/D109636
show more ...
|
#
a6d76cf6 |
| 27-Feb-2021 |
Mehdi Amini <joker.eph@gmail.com> |
Change the error message when `-split-input-file` is used with mlir-opt to make it recognizable by IDEs
By adding the line number of the split point immediately after the file name (separated by `:`
Change the error message when `-split-input-file` is used with mlir-opt to make it recognizable by IDEs
By adding the line number of the split point immediately after the file name (separated by `:`) this is recognized by various tool as a proper location.
Ideally we would want to point to the line of the error, but that would require some very invasive changes I suspect.
Reviewed By: jpienaar
Differential Revision: https://reviews.llvm.org/D93363
show more ...
|
#
30857107 |
| 26-Jan-2020 |
Mehdi Amini <aminim@google.com> |
Mass update the MLIR license header to mention "Part of the LLVM project"
This is an artifact from merging MLIR into LLVM, the file headers are now aligned with the rest of the project.
|
#
56222a06 |
| 23-Dec-2019 |
Mehdi Amini <aminim@google.com> |
Adjust License.txt file to use the LLVM license
PiperOrigin-RevId: 286906740
|
#
0e7edcfe |
| 24-Sep-2019 |
Lei Zhang <antiagainst@google.com> |
Let mlir-translate support -split-input-file
Similar to mlir-opt, having a -split-input-file mode is quite useful in mlir-translate. It allows to put logically related tests in the same test file fo
Let mlir-translate support -split-input-file
Similar to mlir-opt, having a -split-input-file mode is quite useful in mlir-translate. It allows to put logically related tests in the same test file for better organization.
PiperOrigin-RevId: 270805467
show more ...
|