tree 8d290d0f96b7e31c550402abcd581fa6507883f1
parent 769ffda7c2346e3bba26918f7bbd132bcde5101d
author Nicolas Vasilache <nicolasvasilache@users.noreply.github.com> 1678093679 +0100
committer GitHub <noreply@github.com> 1678093679 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkBa1vCRBK7hj4Ov3rIwAANI4IAI0x+KDoMeFpC5vPbqAg/LdL
 AaNzzRGAbEQpDpUYX+emnAYLW5FxrIPWClO+TonTNJor1ozu3hyjzF/IcH3oVtiR
 TCl9b5LIhaGjdEOEXpW5qviwfwGoAFLCj/zC4gWlBfxIKgLsVelQVxx6XDGUEdyz
 JPAerAWe3nCOj/LMqjL9QY9PoglmlUhhIOjyDIyhqXntdxdxobtWcHzzag6/TE50
 mmVfuuInPy7D5aU+GtWBSAwYrfbtDGsxOQDP2iV49RU7RFwlFXoiIncw4Qumfrdw
 z3q//mrirrrmSpvbZ7FIjxBv87UxiuW/AywbLYqzXdKiCffE+2zFmnyw6kUzxyc=
 =5B7k
 -----END PGP SIGNATURE-----
 

Fully retire CanonicalizedSequenceOp (#12467)

This revision fully retires the CanonicalizedSequenceOp and makes the
need for canonicalization / tiling_canonicalization / licm / singleIterationLoopPromotion
explicit in the transform IR.
    
This removes automatic blanket pattern applications which is expected to be beneficial for:
1. reducing compile time
2. reducing surprise (explicit being better than implicit)
3. help surface issues similar to #12444

In the process, plumb the isolatedFromAbove through the API to make the
requirement explicit until we are able to remove it in some future (i.e. with better targeted
canonicalization and greedy pattern rewriter that does not require an isolated from above).