This is an archive of the discontinued LLVM Phabricator instance.

Differential D107915

[mlir][linalg] fixed typo
ClosedPublic

Authored by aartbik on Aug 11 2021, 10:22 AM.

Details

Reviewers
nicolasvasilache
Commits
rGa5ae34afaa45: [mlir][linalg] fixed typo

Diff Detail

Event Timeline

aartbik created this revision.Aug 11 2021, 10:22 AM
Herald added subscribers: wrengr, Chia-hungDuan, dcaballe and 18 others. · View Herald TranscriptAug 11 2021, 10:22 AM
aartbik requested review of this revision.Aug 11 2021, 10:22 AM
Herald added a project: Restricted Project. · View Herald TranscriptAug 11 2021, 10:22 AM
Herald added subscribers: limo1996, stephenneuendorffer, nicolasvasilache. · View Herald Transcript
aartbik added a reviewer: nicolasvasilache.Aug 11 2021, 10:23 AM
Harbormaster completed remote builds in B119101: Diff 365790.Aug 11 2021, 10:53 AM
This revision was not accepted when it landed; it landed in state Needs Review.Aug 11 2021, 11:59 AM
Closed by commit rGa5ae34afaa45: [mlir][linalg] fixed typo (authored by aartbik). · Explain Why
This revision was automatically updated to reflect the committed changes.
aartbik added a commit: rGa5ae34afaa45: [mlir][linalg] fixed typo.

Revision Contents

PathSize
mlir/
docs/
Rationale/
2 lines

Diff 365815

mlir/docs/Rationale/RationaleLinalgDialect.md

Show First 20 Lines • Show All 541 Lines • ▼ Show 20 Lines
models](http://homepages.inf.ed.ac.uk/hleather/publications/2009_autofeatures_cgo.pdf). models](http://homepages.inf.ed.ac.uk/hleather/publications/2009_autofeatures_cgo.pdf).
### Extensibility and Future-Proofness<a name="future"></a> ### Extensibility and Future-Proofness<a name="future"></a>
MLIR allows defining IR for structured control flow and structured MLIR allows defining IR for structured control flow and structured
data types. We choose to take advantage of these properties for the data types. We choose to take advantage of these properties for the
reasons described above. reasons described above.
In particular, the `MemRefType` represents dense non-contiguous memory regions. In particular, the `MemRefType` represents dense non-contiguous memory regions.
This structure should extend beyond simple dense data types and generalize to This structure should extend beyond simple dense data types and generalize to
ragged, sparse and mixed dens/sparse tensors as well as to trees, hash tables, ragged, sparse and mixed dense/sparse tensors as well as to trees, hash tables,
tables of records and maybe even graphs. tables of records and maybe even graphs.
For such more advanced data types, the control-flow required to traverse the For such more advanced data types, the control-flow required to traverse the
data structures, termination conditions, etc are much less simple to analyze and data structures, termination conditions, etc are much less simple to analyze and
characterize statically. As a consequence we need to also design solutions that characterize statically. As a consequence we need to also design solutions that
stand a chance of evolving into runtime-adaptive computations (e.g. stand a chance of evolving into runtime-adaptive computations (e.g.
inspector-executor in which an *inspector* runs a cheap runtime inspector-executor in which an *inspector* runs a cheap runtime
analysis on the data to configure how the *executor* should run). analysis on the data to configure how the *executor* should run).
▲ Show 20 Lines • Show All 64 Lines • Show Last 20 Lines