projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1d4d2cc) | patch
[polly] Remove last instances of -analyze
authorArthur Eubanks <aeubanks@google.com>
Tue, 22 Mar 2022 00:41:06 +0000 (17:41 -0700)
committerArthur Eubanks <aeubanks@google.com>
Thu, 24 Mar 2022 16:47:43 +0000 (09:47 -0700)
commitcaf6af2ed77b1f3509583ecf285b589972c8a67c
treeaa619d763170aaf187463e4359bf8e8efaa513fctree | snapshot
parent1d4d2cceda82514f94d8128ad8404a08f74e7474commit | diff
[polly] Remove last instances of -analyze

As mentioned in D120782, the loop block order can be different depending
on if LoopInfo is incrementally updated or freshly computed.

Reviewed By: Meinersbur

Differential Revision: https://reviews.llvm.org/D122195
polly/test/CodeGen/loop_with_condition_nested.ll diff | blob | history
polly/test/CodeGen/single_loop_param_less_equal.ll diff | blob | history
Domain: System / Toolchain;