Details
Diff Detail
Event Timeline
Thanks for adding this!
lib/Transforms/Scalar/LoopInterchange.cpp | ||
---|---|---|
596–600 | Based on the experience in the inliner, it's helpful to emit the estimated cost and the threshold for such remarks. Then the user would know how much to lower the threshold, etc. You may want to issue this in inProfitable. | |
1002 | "Unable to analyze loop" is probably a better wording. Alternatively you could emit the specific reasons under currentLimitations(). | |
test/Transforms/LoopInterchange/loop-interchange-optimization-remarks.ll | ||
59 | Either have some minimal source line debug info or use the YAML output (-pass-remarks-output) rather than -pass-remarks= which would have the function name in the remark record. You should be able to find some examples for both of these approaches in the testsuite. |
lib/Transforms/Scalar/LoopInterchange.cpp | ||
---|---|---|
1002 | I've added more optimization remarks to currentLimitations().} |
lib/Transforms/Scalar/LoopInterchange.cpp | ||
---|---|---|
596–600 | Are you planning to address this too? | |
929–934 | Indentation seems off, you may want to clang-format the diff. | |
test/Transforms/LoopInterchange/loop-interchange-optimization-remarks.ll | ||
59 | This is actually easier to read if you include the full YAML record verbatim rather than just part of the line/record. |
LGTM with one nit below. Thanks!
lib/Transforms/Scalar/LoopInterchange.cpp | ||
---|---|---|
813–881 | Please use different remark identifier for each remark ("CurrentLimitation" currently). This way we can measure the different failing cases without parsing the text of the remark. |
Thanks Adam! I added unique identifiers for CurrentLimitations remarks. I will commit this in a bit, when I have more time on hand.
Based on the experience in the inliner, it's helpful to emit the estimated cost and the threshold for such remarks. Then the user would know how much to lower the threshold, etc. You may want to issue this in inProfitable.