Skip to content

MemoryDependenceAnalysis: Consider a pointer clobbered if it is saved #142096

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

wzssyqa
Copy link
Contributor

@wzssyqa wzssyqa commented May 30, 2025

In MemoryDependenceResults::getSimplePointerDependencyFrom, when we find the instruction that a LoadInst depends, if we find an store instruction that save the pointer used by LoadInst, we consider the pointer may be clobbered.

In MemoryDependenceResults::getSimplePointerDependencyFrom, when
we find the instruction that a LoadInst depends, if we find an
store instruction that save the pointer used by LoadInst, we consider
the pointer may be clobbered.
@llvmbot
Copy link
Member

llvmbot commented May 30, 2025

@llvm/pr-subscribers-llvm-analysis

Author: YunQiang Su (wzssyqa)

Changes

In MemoryDependenceResults::getSimplePointerDependencyFrom, when we find the instruction that a LoadInst depends, if we find an store instruction that save the pointer used by LoadInst, we consider the pointer may be clobbered.


Full diff: https://github.com/llvm/llvm-project/pull/142096.diff

1 Files Affected:

  • (modified) llvm/lib/Analysis/MemoryDependenceAnalysis.cpp (+5)
diff --git a/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp b/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
index f062189bac6a0..00f36b9e088ad 100644
--- a/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
+++ b/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
@@ -564,6 +564,11 @@ MemDepResult MemoryDependenceResults::getSimplePointerDependencyFrom(
         if (!QueryInst || QueryInst->isVolatile())
           return MemDepResult::getClobber(SI);
 
+      // If we store the pointer of QueryInst, it is danger due to that the address
+      // may be modified with other reference.
+      if (QueryInst && QueryInst->getOperand(0) == SI->getOperand(0))
+        return MemDepResult::getClobber(SI);
+
       // If alias analysis can tell that this store is guaranteed to not modify
       // the query pointer, ignore it.  Use getModRefInfo to handle cases where
       // the query pointer points to constant memory etc.

Copy link

⚠️ C/C++ code formatter, clang-format found issues in your code. ⚠️

You can test this locally with the following command:
git-clang-format --diff HEAD~1 HEAD --extensions cpp -- llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
View the diff from clang-format here.
diff --git a/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp b/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
index 00f36b9e0..a907e22ba 100644
--- a/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
+++ b/llvm/lib/Analysis/MemoryDependenceAnalysis.cpp
@@ -564,8 +564,8 @@ MemDepResult MemoryDependenceResults::getSimplePointerDependencyFrom(
         if (!QueryInst || QueryInst->isVolatile())
           return MemDepResult::getClobber(SI);
 
-      // If we store the pointer of QueryInst, it is danger due to that the address
-      // may be modified with other reference.
+      // If we store the pointer of QueryInst, it is danger due to that the
+      // address may be modified with other reference.
       if (QueryInst && QueryInst->getOperand(0) == SI->getOperand(0))
         return MemDepResult::getClobber(SI);
 

@wzssyqa
Copy link
Contributor Author

wzssyqa commented May 30, 2025

I find this problem when working on x264.
The attached is the IR file.

./bin/opt --passes="default<O3>" x264.ll -S -o xx.ll

can reproduce this problem.

The difference is in function x264_8_macroblock_cache_allocate:
a load instruction

%82 = load ptr, ptr %slice_table, align 16, !tbaa !545

in baiscblock cond.end380 is remove mistakenly.

In fact the contents of ptr %slice_table is clobbered in while.body.

For C code, please see:
https://github.com/ShiftMediaProject/x264/blob/2597c3645a721f4ab1870f13a3751edf78328ff3/common/macroblock.c#L248

x264.tgz

I failed to reduce this cases, thus I cannot figure out a test case.

Copy link
Contributor

@nikic nikic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be handled by AA/CaptureTracking. Needs a reduced reproducer to understand why it fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants