<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/mlir/test/Integration/Dialect/SparseTensor/python/test_SpMM.py, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>[mlir][sparse] fix bug with all-dense assembler (#108615)</title>
<updated>2024-09-14T00:24:48+00:00</updated>
<author>
<name>Aart Bik</name>
<email>ajcbik@google.com</email>
</author>
<published>2024-09-14T00:24:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=0e34dbb4f452013eab89a0a8f04a436ff6c408d4'/>
<id>0e34dbb4f452013eab89a0a8f04a436ff6c408d4</id>
<content type='text'>
When only all-dense "sparse" tensors occur in a function prototype, the
assembler would skip the method conversion purely based on input/output
counts. It should rewrite based on the presence of any annotation,
however.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When only all-dense "sparse" tensors occur in a function prototype, the
assembler would skip the method conversion purely based on input/output
counts. It should rewrite based on the presence of any annotation,
however.</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse][pybind][CAPI] remove LevelType enum from CAPI, constru… (#81682)</title>
<updated>2024-02-14T00:45:22+00:00</updated>
<author>
<name>Peiming Liu</name>
<email>36770114+PeimingLiu@users.noreply.github.com</email>
</author>
<published>2024-02-14T00:45:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=429919e32823ad735a19ab385f37e313512cedde'/>
<id>429919e32823ad735a19ab385f37e313512cedde</id>
<content type='text'>
…ct LevelType from LevelFormat and properties instead.

**Rationale**
We used to explicitly declare every possible combination between
`LevelFormat` and `LevelProperties`, and it now becomes difficult to
scale as more properties/level formats are going to be introduced.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
…ct LevelType from LevelFormat and properties instead.

**Rationale**
We used to explicitly declare every possible combination between
`LevelFormat` and `LevelProperties`, and it now becomes difficult to
scale as more properties/level formats are going to be introduced.</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse] rename DimLevelType to LevelType (#73561)</title>
<updated>2023-11-27T22:27:52+00:00</updated>
<author>
<name>Aart Bik</name>
<email>39774503+aartbik@users.noreply.github.com</email>
</author>
<published>2023-11-27T22:27:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=1944c4f76b47c0b86c91845987baca24fd4775f8'/>
<id>1944c4f76b47c0b86c91845987baca24fd4775f8</id>
<content type='text'>
The "Dim" prefix is a legacy left-over that no longer makes sense, since
we have a very strict "Dimension" vs. "Level" definition for sparse
tensor types and their storage.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The "Dim" prefix is a legacy left-over that no longer makes sense, since
we have a very strict "Dimension" vs. "Level" definition for sparse
tensor types and their storage.</pre>
</div>
</content>
</entry>
<entry>
<title>Changed all code and comments that used the phrase "sparse compiler" to instead use "sparsifier" (#71875)</title>
<updated>2023-11-15T20:12:35+00:00</updated>
<author>
<name>Tim Harvey</name>
<email>146767459+TimAtGoogle@users.noreply.github.com</email>
</author>
<published>2023-11-15T20:12:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=dce7a7cf69a3ef76153c8d04fc3ad75bd7421ffc'/>
<id>dce7a7cf69a3ef76153c8d04fc3ad75bd7421ffc</id>
<content type='text'>
The changes in this p.r. mostly center around the tests that use the
flag sparse_compiler (also: sparse-compiler).</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The changes in this p.r. mostly center around the tests that use the
flag sparse_compiler (also: sparse-compiler).</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse] add COO to python tests (#70090)</title>
<updated>2023-10-24T19:48:46+00:00</updated>
<author>
<name>Aart Bik</name>
<email>39774503+aartbik@users.noreply.github.com</email>
</author>
<published>2023-10-24T19:48:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=260dbb45ac2482695a6fb0c55dcf4b693636f0bf'/>
<id>260dbb45ac2482695a6fb0c55dcf4b693636f0bf</id>
<content type='text'>
also typo fix</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
also typo fix</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse] extend sparse output test (#69986)</title>
<updated>2023-10-24T04:33:54+00:00</updated>
<author>
<name>Aart Bik</name>
<email>39774503+aartbik@users.noreply.github.com</email>
</author>
<published>2023-10-24T04:33:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=ed2d0b0e9b6c56ed5bb5669d07a6036d087464b8'/>
<id>ed2d0b0e9b6c56ed5bb5669d07a6036d087464b8</id>
<content type='text'>
This adds COO and loose compressed to output testing. Also prepares BSR
for output testing, but needs the conversion to work first. Cleanup of
stale TODOs</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds COO and loose compressed to output testing. Also prepares BSR
for output testing, but needs the conversion to work first. Cleanup of
stale TODOs</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse] Populate lvlToDim (#68937)</title>
<updated>2023-10-17T20:09:39+00:00</updated>
<author>
<name>Yinying Li</name>
<email>107574043+yinying-lisa-li@users.noreply.github.com</email>
</author>
<published>2023-10-17T20:09:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=d4088e7d5f4849a4385a568b675d8c99c986d581'/>
<id>d4088e7d5f4849a4385a568b675d8c99c986d581</id>
<content type='text'>
Updates:
1. Infer lvlToDim from dimToLvl
2. Add more tests for block sparsity
3. Finish TODOs related to lvlToDim, including adding lvlToDim to python
binding

Verification of lvlToDim that user provides will be implemented in the
next PR.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Updates:
1. Infer lvlToDim from dimToLvl
2. Add more tests for block sparsity
3. Finish TODOs related to lvlToDim, including adding lvlToDim to python
binding

Verification of lvlToDim that user provides will be implemented in the
next PR.</pre>
</div>
</content>
</entry>
<entry>
<title>[mlir][sparse] Combining `dimOrdering`+`higherOrdering` fields into `dimToLvl`</title>
<updated>2023-05-30T22:19:50+00:00</updated>
<author>
<name>wren romano</name>
<email>2998727+wrengr@users.noreply.github.com</email>
</author>
<published>2023-05-30T20:16:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=76647fce136a362a30ee2434cce765dee9924d74'/>
<id>76647fce136a362a30ee2434cce765dee9924d74</id>
<content type='text'>
This is a major step along the way towards the new STEA design.  While a great deal of this patch is simple renaming, there are several significant changes as well.  I've done my best to ensure that this patch retains the previous behavior and error-conditions, even though those are at odds with the eventual intended semantics of the `dimToLvl` mapping.  Since the majority of the compiler does not yet support non-permutations, I've also added explicit assertions in places that previously had implicitly assumed it was dealing with permutations.

Reviewed By: aartbik

Differential Revision: https://reviews.llvm.org/D151505
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is a major step along the way towards the new STEA design.  While a great deal of this patch is simple renaming, there are several significant changes as well.  I've done my best to ensure that this patch retains the previous behavior and error-conditions, even though those are at odds with the eventual intended semantics of the `dimToLvl` mapping.  Since the majority of the compiler does not yet support non-permutations, I've also added explicit assertions in places that previously had implicitly assumed it was dealing with permutations.

Reviewed By: aartbik

Differential Revision: https://reviews.llvm.org/D151505
</pre>
</div>
</content>
</entry>
<entry>
<title>[NFC][Py Reformat] Reformat python files in mlir subdir</title>
<updated>2023-05-26T06:05:40+00:00</updated>
<author>
<name>Tobias Hieta</name>
<email>tobias@hieta.se</email>
</author>
<published>2023-05-17T14:53:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=f9008e6366c2496b1ca1785b891d5578174ad63e'/>
<id>f9008e6366c2496b1ca1785b891d5578174ad63e</id>
<content type='text'>
This is an ongoing series of commits that are reformatting our
Python code.

Reformatting is done with `black`.

If you end up having problems merging this commit because you
have made changes to a python file, the best way to handle that
is to run git checkout --ours &lt;yourfile&gt; and then reformat it
with black.

If you run into any problems, post to discourse about it and
we will try to help.

RFC Thread below:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential Revision: https://reviews.llvm.org/D150782
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is an ongoing series of commits that are reformatting our
Python code.

Reformatting is done with `black`.

If you end up having problems merging this commit because you
have made changes to a python file, the best way to handle that
is to run git checkout --ours &lt;yourfile&gt; and then reformat it
with black.

If you run into any problems, post to discourse about it and
we will try to help.

RFC Thread below:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential Revision: https://reviews.llvm.org/D150782
</pre>
</div>
</content>
</entry>
<entry>
<title>Reland "[mlir] Make the vast majority of intgration and runner tests work on Windows"</title>
<updated>2023-02-15T18:14:43+00:00</updated>
<author>
<name>Markus Böck</name>
<email>markus.boeck02@gmail.com</email>
</author>
<published>2023-02-15T17:57:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=9048ea28da954f720eea5cf551c29ccebac2340e'/>
<id>9048ea28da954f720eea5cf551c29ccebac2340e</id>
<content type='text'>
This reverts commit 5561e174117ff395d65b6978d04b62c1a1275138

The logic was moved from cmake into lit fixing the issue that lead to the revert and potentially others with multi-config cmake generators

Differential Revision: https://reviews.llvm.org/D143925
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 5561e174117ff395d65b6978d04b62c1a1275138

The logic was moved from cmake into lit fixing the issue that lead to the revert and potentially others with multi-config cmake generators

Differential Revision: https://reviews.llvm.org/D143925
</pre>
</div>
</content>
</entry>
</feed>
