[PATCH] D85818: [UnifyFunctionExitNodes] Fix Modified status for unreachable blocks

serge via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 9 01:52:27 PDT 2020


serge-sans-paille accepted this revision.
serge-sans-paille added a comment.
This revision is now accepted and ready to land.

LGTM



================
Comment at: llvm/test/Transforms/UnifyFunctionExitNodes/unreachable-blocks-status.ll:3
+
+; The pass did previously not report the correct Modified status in the case
+; where a function had at most one return block, and an unified unreachable
----------------
bjope wrote:
> I guess one would have neeed to enable EXPENSIVE_CHECKS for this test case to fail in the past (but only since the check was addded to EXPENSIVE_CHECKS). Could it be worth the trouble to use -debug-pass=Details and check that the pass returns that it has modified both @foo and @bar? In some sense getting rid of the dependency to EXPENSIVE_CHECKS.
> 
> On the other hand, I'm not sure if -debug-pass=Details works with new-pm. But mergereturn has not been ported to the new-pm either, so I'm not sure about the future plans for the pass. Maybe we shouldn't spend too much time here. So I'm happy either way.
>  
I think the test is fine as is, if it was triggering the error before that patch under EXPENSIVE_CHECKS


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D85818/new/

https://reviews.llvm.org/D85818



More information about the llvm-commits mailing list