llvm-project.git/llvm/lib/Transforms/Scalar/LoopUnrollAndJamPass.cpp, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [UnrollAndJam] Do not preserve loop nests if a loop was fully unrolled. (#133510) 2025-03-29T19:21:34+00:00 David Green david.green@arm.com 2025-03-29T19:21:34+00:00 3ef33066bb32a9d9b76d72c6de6a7ae9ff72ddcc If UnJ completely unrolls a loop and removes it entirely, the loop remains in the current loop nest. If the loop nest gets reused the loops will no longer be valid. As there is no way to remove a loop from a LoopNest, this patch removes the preserve of the LoopNestAnalysis so that it will be regenerated. Fixes #124518 
If UnJ completely unrolls a loop and removes it entirely, the loop
remains in the current loop nest. If the loop nest gets reused the loops
will no longer be valid. As there is no way to remove a loop from a
LoopNest, this patch removes the preserve of the LoopNestAnalysis so
that it will be regenerated.

Fixes #124518
 [Scalar] Remove unused includes (NFC) (#114645) 2024-11-02T15:32:26+00:00 Kazu Hirata kazu@google.com 2024-11-02T15:32:26+00:00 94f9cbbe49b4c836cfbed046637cdc0c63a4a083 Identified with misc-include-cleaner. 
Identified with misc-include-cleaner.
 [LoopUnroll] Consider convergence control tokens when unrolling (#91715) 2024-06-06T07:43:46+00:00 Sameer Sahasrabuddhe sameer.sahasrabuddhe@amd.com 2024-06-06T07:43:46+00:00 e0ac087ff004f7a63ba64b9685f4f098d6ee54c5 - There is no restriction on a loop with controlled convergent operations when the relevant tokens are defined and used within the loop. - When a token defined outside a loop is used inside (also called a loop convergence heart), unrolling is allowed only in the absence of remainder or runtime checks. - When a token defined inside a loop is used outside, such a loop is said to be "extended". This loop can only be unrolled by also duplicating the extended part lying outside the loop. Such unrolling is disabled for now. - Clean up loop hearts: When unrolling a loop with a heart, duplicating the heart will introduce multiple static uses of a convergence control token in a cycle that does not contain its definition. This violates the static rules for tokens, and needs to be cleaned up into a single occurrence of the intrinsic. - Spell out the initializer for UnrollLoopOptions to improve readability. Original implementation [D85605] by Nicolai Haehnle <nicolai.haehnle@amd.com>. 
- There is no restriction on a loop with controlled convergent
operations when
  the relevant tokens are defined and used within the loop.

- When a token defined outside a loop is used inside (also called a loop
convergence heart), unrolling is allowed only in the absence of
remainder or
  runtime checks.

- When a token defined inside a loop is used outside, such a loop is
said to be
"extended". This loop can only be unrolled by also duplicating the
extended part
  lying outside the loop. Such unrolling is disabled for now.

- Clean up loop hearts: When unrolling a loop with a heart, duplicating
the
heart will introduce multiple static uses of a convergence control token
in a
cycle that does not contain its definition. This violates the static
rules for
tokens, and needs to be cleaned up into a single occurrence of the
intrinsic.

- Spell out the initializer for UnrollLoopOptions to improve
readability.


Original implementation [D85605] by Nicolai Haehnle
<nicolai.haehnle@amd.com>.
 [Transforms] Use StringRef::starts_with/ends_with instead of startswith/endswith. NFC. 2023-11-06T16:50:18+00:00 Simon Pilgrim llvm-dev@redking.me.uk 2023-11-06T16:47:50+00:00 3ca4fe80d44d4e62b1cd34b6312f61f07cfb3f82 startswith/endswith wrap starts_with/ends_with and will eventually go away (to more closely match string_view) 
startswith/endswith wrap starts_with/ends_with and will eventually go away (to more closely match string_view)
[LoopUnroll] Fold variable only used in assert into the assert 2023-09-27T11:19:18+00:00 Benjamin Kramer benny.kra@googlemail.com 2023-09-27T11:19:18+00:00 4731623f81c47d9e879d845dee0609b84daa9efd Avoids warnings in Release builds. NFCI. 
Avoids warnings in Release builds. NFCI.
[LoopUnroll] Store more information in UnrollCostEstimator (NFCI) 2023-09-27T10:06:13+00:00 Nikita Popov npopov@redhat.com 2023-09-27T09:59:44+00:00 296671f059198185bedc3eba80056ebf4bc7ad30 Instead of having ApproximateLoopSize() use a bunch of out parameters, from which we later construct an UnrollCostEstimator, directly construct UnrollCostEstimator which holds all the information derived from loop analysis. This makes it easier to add additional metrics in the future. 
Instead of having ApproximateLoopSize() use a bunch of out parameters,
from which we later construct an UnrollCostEstimator, directly
construct UnrollCostEstimator which holds all the information
derived from loop analysis. This makes it easier to add additional
metrics in the future.
Remove several no longer needed includes. NFCI 2023-04-17T11:54:19+00:00 Bjorn Pettersson bjorn.a.pettersson@ericsson.com 2023-04-15T08:16:09+00:00 a20f7efbc587a213868b494d3d34a8cbeaff04ab Mostly removing includes of InitializePasses.h and Pass.h in passes that no longer has support for the legacy PM. 
Mostly removing includes of InitializePasses.h and Pass.h in
passes that no longer has support for the legacy PM.
[LoopUnrollAndJam] Remove legacy pass 2023-02-15T01:23:15+00:00 Fangrui Song i@maskray.me 2023-02-15T01:23:15+00:00 766065aa6553df4030e6f563b066410fcee9d751 Following recent changes to remove non-core features of the legacy PM/optimization pipeline. 
Following recent changes to remove non-core features of the legacy PM/optimization pipeline.
[Transforms,CodeGen] std::optional::value => operator*/operator-> 2022-12-16T23:21:27+00:00 Fangrui Song i@maskray.me 2022-12-16T23:21:27+00:00 51b685734b0e185bca9d0eec66b3bcb636ed9c02 value() has undesired exception checking semantics and calls __throw_bad_optional_access in libc++. Moreover, the API is unavailable without _LIBCPP_NO_EXCEPTIONS on older Mach-O platforms (see _LIBCPP_AVAILABILITY_BAD_OPTIONAL_ACCESS). 
value() has undesired exception checking semantics and calls
__throw_bad_optional_access in libc++. Moreover, the API is unavailable without
_LIBCPP_NO_EXCEPTIONS on older Mach-O platforms (see
_LIBCPP_AVAILABILITY_BAD_OPTIONAL_ACCESS).
Don't include Optional.h 2022-12-15T05:16:22+00:00 Kazu Hirata kazu@google.com 2022-12-15T05:16:22+00:00 6eb0b0a0452a4c53ceb1156afd17764fbff51111 These files no longer use llvm::Optional. 
These files no longer use llvm::Optional.