llvm-project.git/llvm/test/Transforms/LoopVersioningLICM/loopversioningLICM2.ll, branch users/nico/python-2

[LoopVersioningLICM] Only mark pointers with generated checks as noalias (#135168)

2025-05-12T09:15:22+00:00

Currently when we version a loop all loads and stores have the noalias
metadata added to them. If there were some pointers that could not be
analysed, and thus we could not generate runtime aliasing checks for,
then we should not mark loads and stores using these pointers as
noalias.

This is done by getting rid of setNoAliasToLoop and instead using
annotateLoopWithNoAlias, as that already correctly handles partial alias
information. This does result in slightly different aliasing metadata
being generated, but it looks like it's more precise.

Currently this doesn't result in any change to the transforms that
LoopVersioningLICM does, as LoopAccessAnalysis discards all results if
it couldn't analyse every pointer leading to no loop versioning
happening, but an upcoming patch will change that and we need this first
otherwise we incorrectly mark some pointers as noalias even when they
aren't.

[LoopVersioningLICM] Convert tests to opaque pointers (NFC)

2023-01-04T16:17:17+00:00

[NFC][1/n] Remove -enable-new-pm=0 flags from lit tests

2022-09-19T16:57:37+00:00

This is the first patch in a series intended for removing flag
-enable-new-pm=0 from lit tests. This is part of a bigger
effort of completely removing legacy code related to legacy
pass manager in favor of currently default new pass manager.

In this patch flag has been removed only from tests where no significant
change has been required because checks has been duplicated for
both PMs.

Reviewed By: fhahn

Differential Revision: https://reviews.llvm.org/D134150

[LICM] Remove AST-based implementation

2021-08-18T18:21:53+00:00

MSSA-based LICM has been enabled by default for a few years now.
This drops the old AST-based implementation. Using loop(licm) will
result in a fatal error, the use of loop-mssa(licm) is required
(or just licm, which defaults to loop-mssa).

Note that the core canSinkOrHoistInst() logic has to retain AST
support for now, because it is shared with LoopSink.

Differential Revision: https://reviews.llvm.org/D108244

[LoopUtils] Fix incorrect RT check bounds of loop-invariant mem accesses

2021-07-19T11:38:24+00:00

This fixes the lower and upper bound calculation of a
RuntimeCheckingPtrGroup when it has more than one loop
invariant pointers. Resolves PR50686.

Reviewed By: fhahn

Differential Revision: https://reviews.llvm.org/D104148

[llvm] Update tests that got missed in adee485adf84ae8a.

2021-06-23T09:29:58+00:00

[NewPM][opt] Run the "default" AA pipeline by default

2021-01-22T05:08:54+00:00

We tend to assume that the AA pipeline is by default the default AA
pipeline and it's confusing when it's empty instead.

PR48779

Initially reverted due to BasicAA running analyses in an unspecified
order (multiple function calls as parameters), fixed by fetching
analyses before the call to construct BasicAA.

Reviewed By: asbirlea

Differential Revision: https://reviews.llvm.org/D95117

Revert "[NewPM][opt] Run the "default" AA pipeline by default"

2021-01-22T04:16:34+00:00

This reverts commit be611431cd1f5c826a55b531db92a63e84323866.

Other/new-pm-lto-defaults.ll failing

[NewPM][opt] Run the "default" AA pipeline by default

2021-01-22T03:46:38+00:00

We tend to assume that the AA pipeline is by default the default AA
pipeline and it's confusing when it's empty instead.

PR48779

Reviewed By: asbirlea

Differential Revision: https://reviews.llvm.org/D95117

[test] Fix Transforms/LoopVersioningLICM under NPM

2020-12-08T05:54:38+00:00

There were already both legacy and new PM RUN lines.
Also make the NPM RUN line actually match the legacy PM RUN line.