[PATCH] D107381: [runtimeunroll] Support multiple exits to latch exit w/epilogue loop

Florian Hahn via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Aug 19 11:16:41 PDT 2021


fhahn added a comment.

In D107381#2955288 <https://reviews.llvm.org/D107381#2955288>, @reames wrote:

> In D107381#2954577 <https://reviews.llvm.org/D107381#2954577>, @bjope wrote:
>
>> I'm seeing the same fault as @alanphipps when having build with LLVM_ENABLE_EXPENSIVE_CHECKS=ON and running the test/Transforms/LoopUnroll/runtime-loop-multiple-exits.ll test case.
>>
>> Should we revert this patch until this has been investigated further?
>
> Should be fixed in 447256f <https://reviews.llvm.org/rG447256f22b4dc125877aed11aac875c03d0228eb>.  If not, please revert both changes and I'll take another look.
>
> I do want to briefly address the revert question though.  I would not revert based on the first report.  There's no reproducer, and (I'm guessing) they're force enabling an internal flag.  That would definitely be an unsupported configuration.  Your second report is a supported configuration failing with an intree reproducer.  Reverting to green in that case would have been completely reasonable.
>
> p.s. Did I miss a buildbot failure on this?  I'm surprised I didn't notice the expensive check failure.  I would have expected a buildbot to report that.

It showed up there https://green.lab.llvm.org/green/job/clang-stage1-cmake-RA-expensive/20179/

But I think for some reason that one does not send emails. I'll check with the maintainers.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D107381



More information about the llvm-commits mailing list