Displaying 5 results from an estimated 5 matches for "outllin".
Did you mean:
outllib
2017 Sep 28
3
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...does a canonicalization step calling
> InstSimplify to canonicalize (so, in this sense it catches more
> stuffs, e.g.:
>
> %x = add %a, 0
> %y = sub %b, 0
> not equivalent
>
> instSimplify(%y) -> add %a, 0
> now they're equivalent.
>
> Note: The current IR outlliner doesn't really use the approach I just
> described, yet, but it's not hard to imagine extending (or rewriting
> it to use a real Global Value number analysis to get instructions that
> are equivalent, for some definition of structural equivalency)
I would also note that we alrea...
2017 Sep 27
0
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...operation and operand
structurally congruent), it also does a canonicalization step calling
InstSimplify to canonicalize (so, in this sense it catches more
stuffs, e.g.:
%x = add %a, 0
%y = sub %b, 0
not equivalent
instSimplify(%y) -> add %a, 0
now they're equivalent.
Note: The current IR outlliner doesn't really use the approach I just
described, yet, but it's not hard to imagine extending (or rewriting
it to use a real Global Value number analysis to get instructions that
are equivalent, for some definition of structural equivalency)
So, I wonder whether you plan to enhance the...
2017 Sep 28
0
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...so does a canonicalization step calling
> InstSimplify to canonicalize (so, in this sense it catches more
> stuffs, e.g.:
>
> %x = add %a, 0
> %y = sub %b, 0
> not equivalent
>
> instSimplify(%y) -> add %a, 0
> now they're equivalent.
>
> Note: The current IR outlliner doesn't really use the approach I just
> described, yet, but it's not hard to imagine extending (or rewriting
> it to use a real Global Value number analysis to get instructions that
> are equivalent, for some definition of structural equivalency)
>
> I would also note tha...
2017 Sep 27
1
[RFC] PT.2 Add IR level interprocedural outliner for code size.
...does a canonicalization step calling
> InstSimplify to canonicalize (so, in this sense it catches more
> stuffs, e.g.:
>
> %x = add %a, 0
> %y = sub %b, 0
> not equivalent
>
> instSimplify(%y) -> add %a, 0
> now they're equivalent.
>
> Note: The current IR outlliner doesn't really use the approach I just
> described, yet, but it's not hard to imagine extending (or rewriting
> it to use a real Global Value number analysis to get instructions that
> are equivalent, for some definition of structural equivalency)
>
> So, I wonder whether...
2017 Sep 27
3
[RFC] PT.2 Add IR level interprocedural outliner for code size.
I think that, given previous discussion on the topic, we might want a split like this:
(1) Search structure
Suffix tree or suffix array.
(2) Numbering/mapping/congruence scheme
Every outliner should implement a function that maps instructions (or whatever structure you want to outline, crazy thoughts…) to integers. That should be passed to the search structure, which will return a list of