================ @@ -1,8 +1,23 @@ -// RUN: %clang_analyze_cc1 -analyzer-checker=core,deadcode.DeadStores,debug.Stats -verify -Wno-unreachable-code -analyzer-max-loop 4 %s +// RUN: %clang_analyze_cc1 \ +// RUN: -analyzer-checker=core,deadcode.DeadStores,debug.Stats \ +// RUN: -Wno-unreachable-code \ +// RUN: -verify=default %s + +// NOTE: analyzer-max-loop option is only meaningful if unroll-loops is false, +// that's why we do not pass it in the first case, as unroll-loops is +// true by default. ---------------- gamesh411 wrote:
You are right, -unroll-loops=true does not unroll all loops. Maybe in the context of these test-cases it may have more truth, but it is misleading to have this comment here. I'll remove the comment, as anyone that needs to later touch these tests would have to look up the interplay between `unroll-loops` and `analyzer-max-loop` anyway. But if you think we should have something here, I'm open for suggestions. https://github.com/llvm/llvm-project/pull/178911 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
