llvm-project/llvm/test/Transforms/LoopRotate
Jamie Schmeiser 5e3ac79690 Loop names used in reporting can grow very large
Summary:
The code for generating a name for loops for various reporting scenarios
created a name by serializing the loop into a string.  This may result in
a very large name for a loop containing many blocks.  Use the getName()
function on the loop instead.

Author: Jamie Schmeiser <schmeise@ca.ibm.com>
Reviewed By: Whitney (Whitney Tsang), aeubanks (Arthur Eubanks)
Differential Revision: https://reviews.llvm.org/D133587
2022-09-09 13:45:14 -04:00
..
RISCV
2009-01-25-SingleEntryPhi.ll
PhiRename-1.ll
PhiSelfReference-1.ll
alloca.ll
basic.ll
call-prepare-for-lto.ll
callbr.ll [IR] Don't treat callbr as indirect terminator 2022-07-18 09:32:08 +02:00
catchret.ll
convergent.ll
crash.ll
dbg-value-duplicates-2.ll
dbg-value-duplicates.ll
dbgvalue.ll
freeze-crash.ll
indirectbr.ll
loopexitinglatch.ll
multiple-deopt-exits.ll
multiple-exits.ll
noalias.ll
nosimplifylatch.ll
oz-disable.ll
phi-dbgvalue.ll
phi-duplicate.ll
pr2639.ll
pr22337.ll
pr33701.ll
pr35210.ll Loop names used in reporting can grow very large 2022-09-09 13:45:14 -04:00
pr37205.ll
pr51981-scev-problem.ll
preserve-loop-simplify.ll
preserve-mssa.ll
preserve-scev.ll
simplifylatch.ll
switch.ll
vect.omp.persistence.ll