Displaying 4 results from an estimated 4 matches for "trippable".
Did you mean:
strippable
2020 Jan 30
2
Writing loop transformations on the right representation is more productive
...b Uday Kumar Reddy Bondhugula <
uday at polymagelabs.com>:
> Hi Michael,
>
> Although the approach to use a higher order in-memory abstraction like the
> loop tree will make it easier than what you have today, if you used MLIR
> for this representation, you already get a round trippable textual format
> that is *very close* to your form. The affine.for/if, std.for/if in MLIR
> are nearly isomorphic to the tree representation you want, and as such,
> this drastically reduces the delta between the in-memory data structures
> your passes want to operate on and what you se...
2018 Apr 25
0
RFC: LLVM Assembly format for ThinLTO Summary
Hi Teresa
Thanks for the proposal. Serializing out the summary in a readable format is very help for debugging and development. Some comments inline.
> On Apr 24, 2018, at 7:43 AM, Teresa Johnson via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi everyone,
>
> I started working on a long-standing request to have the summary dumped in a readable format to text, and
2020 Jan 03
10
Writing loop transformations on the right representation is more productive
In the 2018 LLVM DevMtg [1], I presented some shortcomings of how LLVM
optimizes loops. In summary, the biggest issues are (a) the complexity
of writing a new loop optimization pass (including needing to deal
with a variety of low-level issues, a significant amount of required
boilerplate, the difficulty of analysis preservation, etc.), (b)
independent optimization heuristics and a fixed pass
2018 Apr 24
8
RFC: LLVM Assembly format for ThinLTO Summary
Hi everyone,
I started working on a long-standing request to have the summary dumped in
a readable format to text, and specifically to emit to LLVM assembly.
Proposal below, please let me know your thoughts.
Thanks,
Teresa
*RFC: LLVM Assembly format for ThinLTO