bcm5719-llvm/mlir/lib/Target, branch meklort-10.0.1

[mlir] Fix translation of splat constants to LLVM IR

2020-01-14T11:37:47+00:00

Summary: When converting splat constants for nested sequential LLVM IR types wrapped in MLIR, the constant conversion was erroneously assuming it was always possible to recursively construct a constant of a sequential type given only one value. Instead, wait until all sequential types are unpacked recursively before constructing a scalar constant and wrapping it into the surrounding sequential type. Subscribers: mehdi_amini, rriddle, jpienaar, burmako, shauheen, antiagainst, nicolasvasilache, arpith-jacob, mgester, lucyrfox, aartbik, liufengdb, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D72688

[mlir] NFC: Remove Value::operator* and Value::operator-> now that Value is properly value-typed.

2020-01-11T16:54:39+00:00

Summary: These were temporary methods used to simplify the transition. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D72548

[mlir] Fix -Wrange-loo-analysis warnings

2020-01-02T00:06:04+00:00

for (const auto &x : llvm::zip(..., ...)) -> for (auto x : llvm::zip(..., ...)) The return type of zip() is a wrapper that wraps a tuple of references. > warning: loop variable 'p' is always a copy because the range of type 'detail::zippy &, ArrayRef &>' does not return a reference [-Wrange-loop-analysis]

[mlir] Floating constants for import-llvm

2019-12-27T10:48:24+00:00

Summary: `mlir-translate -import-llvm test.ll` was going into segmentation fault if `test.ll` had `float` or `double` constants. For example, ``` %3 = fadd double 3.030000e+01, %0 ``` Now, it is handled in `Importer::getConstantAsAttr` (similar behaviour as normal integers) Added tests for FP arithmetic Reviewers: ftynse, mehdi_amini Reviewed By: ftynse, mehdi_amini Subscribers: shauheen, mehdi_amini, rriddle, jpienaar, burmako, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D71912

NFC: Replace ValuePtr with Value and remove it now that Value is value-typed.

2019-12-24T00:36:53+00:00

ValuePtr was a temporary typedef during the transition to a value-typed Value. PiperOrigin-RevId: 286945714

Adjust License.txt file to use the LLVM license

2019-12-23T23:33:37+00:00

PiperOrigin-RevId: 286906740

NFC: Introduce new ValuePtr/ValueRef typedefs to simplify the transition to Value being value-typed.

2019-12-23T06:00:23+00:00

This is an initial step to refactoring the representation of OpResult as proposed in: https://groups.google.com/a/tensorflow.org/g/mlir/c/XXzzKhqqF_0/m/v6bKb08WCgAJ This change will make it much simpler to incrementally transition all of the existing code to use value-typed semantics. PiperOrigin-RevId: 286844725

Detemplatize ModuleTranslation::lookupValues

2019-12-19T19:35:57+00:00

This function template has been introduced in the early days of MLIR to work around the absence of common type for ranges of values (operands, block argumeents, vectors, etc). Core IR now provides ValueRange for exactly this purpose. Use it instead of the template parameter. PiperOrigin-RevId: 286431338

NFC: Remove forbidden include of

2019-12-18T19:20:31+00:00

See: https://llvm.org/docs/CodingStandards.html#include-iostream-is-forbidden PiperOrigin-RevId: 286226467

NFC: Cleanup non-conforming usages of namespaces.

2019-12-18T18:46:48+00:00

* Fixes use of anonymous namespace for static methods. * Uses explicit qualifiers(mlir::) instead of wrapping the definition with the namespace. PiperOrigin-RevId: 286222654