aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Language/CPlusPlus/LibStdcpp.cpp
diff options
context:
space:
mode:
authorRamkumar Ramachandra <ramkumar.ramachandra@codasip.com>2025-07-07 12:02:41 +0100
committerGitHub <noreply@github.com>2025-07-07 12:02:41 +0100
commitfb845f93c003e6696d4741f4825541a2c0867c42 (patch)
tree9d52ed4af9a4755d621e10fda0858a97ec9dd0cd /lldb/source/Plugins/Language/CPlusPlus/LibStdcpp.cpp
parente7bcd3f7c743d6e10d26540a8d58648be5a95304 (diff)
downloadllvm-fb845f93c003e6696d4741f4825541a2c0867c42.zip
llvm-fb845f93c003e6696d4741f4825541a2c0867c42.tar.gz
llvm-fb845f93c003e6696d4741f4825541a2c0867c42.tar.bz2
[LAA] Hoist setting condition for RT-checks (#128045)
Strip ShouldRetyWithRuntimeCheck from the DepedenceDistanceStrideAndSizeInfo struct, and free isDependent from the responsibility of setting the condition for when runtime-checks are needed, transferring this responsibility to getDependenceDistanceStrideAndSize. We can have multiple DepType::Unknown dependences that, by themselves, do not trigger the retrying with runtime memory checks, and therefore block vectorization. But once a single FoundNonConstantDistanceDependence is found, the analysis seems to switch to the "LAA: Retrying with memory checks" path and allows all these dependences to be handled via runtime checks. There is hence no rationale for predicating FoundNonConstantDependenceDistance on DepType::Unknown, and removing this predication is one of the side-effects of this patch.
Diffstat (limited to 'lldb/source/Plugins/Language/CPlusPlus/LibStdcpp.cpp')
0 files changed, 0 insertions, 0 deletions