Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-02-06T10:24:21+00:00 2020-02-06T10:24:21+00:00 Dimitry Andric dimitry@andric.com 2020-02-04T23:57:02+00:00 urn:sha1:02420968fcce71ed669b4a87e62c27d65fd8a1c4 This is fixing a build error: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'Region::iterator::difference_type' (aka 'int') in initializer list Fix pr44767 (cherry picked from commit 31fd112eb4a90600e0f340f19053e5715e92ec4c) 2020-01-14T13:06:37+00:00 Benjamin Kramer benny.kra@googlemail.com 2020-01-14T13:06:12+00:00 urn:sha1:df186507e1d07c3ddba091a076ba7a33dbdc5867 2020-01-13T23:51:28+00:00 River Riddle riverriddle@google.com 2020-01-13T23:46:40+00:00 urn:sha1:c7748404920b3674e79059cbbe73b6041a214444 Summary: This enables tracking calls that cross symbol table boundaries. It also simplifies some of the implementation details of CallableOpInterface, i.e. there can only be one region within the callable operation. Depends On D72042 Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D72043 2020-01-13T21:55:50+00:00 River Riddle riverriddle@google.com 2020-01-13T21:44:30+00:00 urn:sha1:cb89c7e3f744c1fede60f7d1c43528654de676bd This was left over debugging. 2020-01-11T16:54:39+00:00 River Riddle riverriddle@google.com 2020-01-11T16:54:04+00:00 urn:sha1:2bdf33cc4c733342fc83081bc7410ac5e9a24f55 Summary: These were temporary methods used to simplify the transition. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D72548 2019-12-31T04:50:07+00:00 River Riddle riverriddle@google.com 2019-12-31T04:49:47+00:00 urn:sha1:0d6ebb4f0dd7ca81bdfc2a210b1d5ef46e0c9587 Summary: A new class is added, IRMultiObjectWithUseList, that allows for representing an IR use list that holds multiple sub values(used in this case for OpResults). This class provides all of the same functionality as the base IRObjectWithUseList, but for specific sub-values. This saves a word per operation result and is a necessary step in optimizing the layout of operation results. For now the use list is placed on the operation itself, so zero-result operations grow by a word. When the work for optimizing layout is finished, this can be moved back to being a trailing object based on memory/runtime benchmarking. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D71955 2019-12-24T00:36:53+00:00 River Riddle riverriddle@google.com 2019-12-23T22:45:01+00:00 urn:sha1:e62a69561fb9d7b1013d2853da68d79a7907fead ValuePtr was a temporary typedef during the transition to a value-typed Value. PiperOrigin-RevId: 286945714 2019-12-24T00:26:15+00:00 River Riddle riverriddle@google.com 2019-12-23T21:05:38+00:00 urn:sha1:5d5bd2e1da29d976cb125dbb3cd097a5e42b2be4 This means that in-place, or root, updates need to use explicit calls to `startRootUpdate`, `finalizeRootUpdate`, and `cancelRootUpdate`. The major benefit of this change is that it enables in-place updates in DialectConversion, which simplifies the FuncOp pattern for example. The major downside to this is that the cases that *may* modify an operation in-place will need an explicit cancel on the failure branches(assuming that they started an update before attempting the transformation). PiperOrigin-RevId: 286933674 2019-12-23T23:33:37+00:00 Mehdi Amini aminim@google.com 2019-12-23T17:35:36+00:00 urn:sha1:56222a0694e4caf35e892d70591417c39fef1185 PiperOrigin-RevId: 286906740 2019-12-23T06:00:23+00:00 River Riddle riverriddle@google.com 2019-12-23T05:59:55+00:00 urn:sha1:35807bc4c5c9d8abc31ba0b2f955a82abf276e12 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