<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/mlir/lib/Support, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-12-31T17:54:16+00:00</updated>
<entry>
<title>[mlir] Make code blocks more consistent</title>
<updated>2019-12-31T17:54:16+00:00</updated>
<author>
<name>Jacques Pienaar</name>
<email>jpienaar@google.com</email>
</author>
<published>2019-12-31T17:52:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=430bba2a0f39b543e66119761d1526d037229936'/>
<id>urn:sha1:430bba2a0f39b543e66119761d1526d037229936</id>
<content type='text'>
Use the same form specification for the same type of code.
</content>
</entry>
<entry>
<title>Adjust License.txt file to use the LLVM license</title>
<updated>2019-12-23T23:33:37+00:00</updated>
<author>
<name>Mehdi Amini</name>
<email>aminim@google.com</email>
</author>
<published>2019-12-23T17:35:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=56222a0694e4caf35e892d70591417c39fef1185'/>
<id>urn:sha1:56222a0694e4caf35e892d70591417c39fef1185</id>
<content type='text'>
PiperOrigin-RevId: 286906740
</content>
</entry>
<entry>
<title>NFC: Remove unnecessary 'llvm::' prefix from uses of llvm symbols declared in `mlir` namespace.</title>
<updated>2019-12-18T17:29:20+00:00</updated>
<author>
<name>River Riddle</name>
<email>riverriddle@google.com</email>
</author>
<published>2019-12-18T17:28:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4562e389a43caa2e30ebf277c12743edafe6a0ac'/>
<id>urn:sha1:4562e389a43caa2e30ebf277c12743edafe6a0ac</id>
<content type='text'>
Aside from being cleaner, this also makes the codebase more consistent.

PiperOrigin-RevId: 286206974
</content>
</entry>
<entry>
<title>mlir-translate: support -verify-diagnostics</title>
<updated>2019-11-07T19:42:46+00:00</updated>
<author>
<name>Alex Zinenko</name>
<email>zinenko@google.com</email>
</author>
<published>2019-11-07T19:42:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=09e8e7107aafcdc61632ed0aabfa63255859e87a'/>
<id>urn:sha1:09e8e7107aafcdc61632ed0aabfa63255859e87a</id>
<content type='text'>
MLIR translation tools can emit diagnostics and we want to be able to check if
it is indeed the case in tests. Reuse the source manager error handlers
provided for mlir-opt to support the verification in mlir-translate. This
requires us to change the signature of the functions that are registered to
translate sources to MLIR: it now takes a source manager instead of a memory
buffer.

PiperOrigin-RevId: 279132972
</content>
</entry>
<entry>
<title>Drop MemRefUtils from the ExecutionEngine</title>
<updated>2019-10-23T14:43:06+00:00</updated>
<author>
<name>Alex Zinenko</name>
<email>zinenko@google.com</email>
</author>
<published>2019-10-23T14:42:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=0d33703f2a4a457253f60e6661615fed28f48fe6'/>
<id>urn:sha1:0d33703f2a4a457253f60e6661615fed28f48fe6</id>
<content type='text'>
The ExecutionEngine was updated recently to only take the LLVM dialect as
input. Memrefs are no longer expected in the signature of the entry point
function by the executor so there is no need to allocate and free them. The
code in MemRefUtils is therefore dead and furthermore out of sync with the
recent evolution of memref type to support strides. Drop it.

PiperOrigin-RevId: 276272302
</content>
</entry>
<entry>
<title>Add missing include to llvm Allocator.h</title>
<updated>2019-10-19T19:11:01+00:00</updated>
<author>
<name>Mehdi Amini</name>
<email>aminim@google.com</email>
</author>
<published>2019-10-19T19:10:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5b1345ff7631ec9c1efd2f6198a49da98793f398'/>
<id>urn:sha1:5b1345ff7631ec9c1efd2f6198a49da98793f398</id>
<content type='text'>
This header is not self-contained otherwise.

PiperOrigin-RevId: 275651582
</content>
</entry>
<entry>
<title>Use llvm.func to define functions with wrapped LLVM IR function type</title>
<updated>2019-10-10T08:34:06+00:00</updated>
<author>
<name>Alex Zinenko</name>
<email>zinenko@google.com</email>
</author>
<published>2019-10-10T08:33:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5e7959a3531c8019052bae3a84a42a67c5857bc9'/>
<id>urn:sha1:5e7959a3531c8019052bae3a84a42a67c5857bc9</id>
<content type='text'>
This function-like operation allows one to define functions that have wrapped
LLVM IR function type, in particular variadic functions. The operation was
added in parallel to the existing lowering flow, this commit only switches the
flow to use it.

Using a custom function type makes the LLVM IR dialect type system more
consistent and avoids complex conversion rules for functions that previously
had to use the built-in function type instead of a wrapped LLVM IR dialect type
and perform conversions during the analysis.

PiperOrigin-RevId: 273910855
</content>
</entry>
<entry>
<title>Add Instance Specific Pass Options.</title>
<updated>2019-10-09T01:23:43+00:00</updated>
<author>
<name>MLIR Team</name>
<email>no-reply@google.com</email>
</author>
<published>2019-10-09T01:23:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=744615123618e000caba27ed9fe3885e79668cb5'/>
<id>urn:sha1:744615123618e000caba27ed9fe3885e79668cb5</id>
<content type='text'>
This allows individual passes to define options structs and for these options to be parsed per instance of the pass while building the pass pipeline from the command line provided textual specification.

The user can specify these per-instance pipeline options like so:
```
struct MyPassOptions : public PassOptions&lt;MyPassOptions&gt; {
  Option&lt;int&gt; exampleOption{*this, "flag-name", llvm::cl::desc("...")};
  List&lt;int&gt; exampleListOption{*this, "list-flag-name", llvm::cl::desc("...")};
};

static PassRegistration&lt;MyPass, MyPassOptions&gt; pass("my-pass", "description");
```

PiperOrigin-RevId: 273650140
</content>
</entry>
<entry>
<title>Fix JitRunner.cpp Error creation pattern and reactivate tests.</title>
<updated>2019-09-27T16:56:40+00:00</updated>
<author>
<name>Nicolas Vasilache</name>
<email>ntv@google.com</email>
</author>
<published>2019-09-27T16:44:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6543e99fe51b9077d8185ba9741770adc5f7cde5'/>
<id>urn:sha1:6543e99fe51b9077d8185ba9741770adc5f7cde5</id>
<content type='text'>
linalg_integration_test.mlir and simple.mlir were temporarily disabled due to an OSS-only failure.

The issue is that, once created, an llvm::Error must be explicitly checked before it can be discarded or overwritten.

This CL fixes the issue and reenable the test.

PiperOrigin-RevId: 271589651
</content>
</entry>
<entry>
<title>Drop support for memrefs from JitRunner</title>
<updated>2019-09-26T12:42:01+00:00</updated>
<author>
<name>Alex Zinenko</name>
<email>zinenko@google.com</email>
</author>
<published>2019-09-26T12:41:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=99be3351b874444498c03a87e2aeec6f2f8c208d'/>
<id>urn:sha1:99be3351b874444498c03a87e2aeec6f2f8c208d</id>
<content type='text'>
The support for functions taking and returning memrefs of floats was introduced
in the first version of the runner, created before MLIR had reliable lowering
of allocation/deallocation to library calls.  It forcibly runs MLIR
transformation convering affine, loop and standard dialects into the LLVM
dialect, unlike the other runner flows that accept the LLVM dialect directly.
Memref support leads to more complex layering and is generally fragile.  Drop
it in favor of functions returning a scalar, or library-based function calls to
print memrefs and other data structures.

PiperOrigin-RevId: 271330839
</content>
</entry>
</feed>
