summaryrefslogtreecommitdiffstats
path: root/mlir/test/lib/TestDialect/TestDialect.h
Commit message (Collapse)AuthorAgeFilesLines
* Adjust License.txt file to use the LLVM licenseMehdi Amini2019-12-231-13/+4
| | | | PiperOrigin-RevId: 286906740
* De-duplicate EnumAttr overrides by defining defaultsLei Zhang2019-11-251-0/+2
| | | | | | | EnumAttr should provide meaningful defaults so concrete instances do not need to duplicate the fields. PiperOrigin-RevId: 282398431
* Add an option to print an operation if a diagnostic is emitted on itRiver Riddle2019-11-121-5/+6
| | | | | | It is often helpful to inspect the operation that the error/warning/remark/etc. originated from, especially in the context of debugging or in the case of a verifier failure. This change adds an option 'mlir-print-op-on-diagnostic' that attaches the operation as a note to any diagnostic that is emitted on it via Operation::emit(Error|Warning|Remark). In the case of an error, the operation is printed in the generic form. PiperOrigin-RevId: 280021438
* Add a test.symbol_scope operation that has the SymbolTable Traits to the ↵Mehdi Amini2019-10-311-0/+1
| | | | | | Test dialect PiperOrigin-RevId: 277741687
* Add support for function result attributes.Sean Silva2019-10-181-0/+8
| | | | | | | | | | | | | | | | | | | | | | This allows dialect-specific attributes to be attached to func results. (or more specifically, FunctionLike ops). For example: ``` func @f() -> (i32 {my_dialect.some_attr = 3}) ``` This attaches my_dialect.some_attr with value 3 to the first result of func @f. Another more complex example: ``` func @g() -> (i32, f32 {my_dialect.some_attr = "foo", other_dialect.some_other_attr = [1,2,3]}, i1) ``` Here, the second result has two attributes attached. PiperOrigin-RevId: 275564165
* Add InferTypeOpTrait & enable generating its member function definitionJacques Pienaar2019-09-291-0/+1
| | | | | | | | | | Use OpInterfaces to add an interface for ops defining a return type function. This change does not use this trait in any meaningful way, I'll use it in a follow up to generalize and unify some of the op type traits/constraints. Also, currently the infer type function can only be manually specified in C++, that should rather be the fallback in future. PiperOrigin-RevId: 271883746
* Add interfaces for call-like/callable operations.River Riddle2019-09-231-0/+1
| | | | | | | | | | | These two operation interfaces will be used in a followup to support building a callgraph: * CallOpInterface - Operations providing this interface are call-like, and have a "call" target. A call target may be a symbol reference, via SymbolRefAttr, or a SSA value. * CallableOpInterface - Operations providing this interfaces define destinations to call-like operations, e.g. FuncOp. These operations may define any number of callable regions. PiperOrigin-RevId: 270723300
* Add tests for broadcastable traitSmit Hinsu2019-07-191-0/+1
| | | | PiperOrigin-RevId: 258637509
* Respect the user provided type when parsing StringAttr.River Riddle2019-06-271-0/+1
| | | | PiperOrigin-RevId: 255532918
* Split test-specific passes out of mlir-optNicolas Vasilache2019-06-241-0/+46
Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
OpenPOWER on IntegriCloud