Displaying 5 results from an estimated 5 matches for "memoryuseordef".
2016 Oct 30
0
[PATCH] D26127: [MemorySSA] Repair AccessList invariants after insertion of new MemoryUseOrDef.
On Sun, Oct 30, 2016 at 4:08 PM, Bryant Wong <
3.14472+reviews.llvm.org at gmail.com> wrote:
>
> On Sun, Oct 30, 2016 at 6:48 PM, Daniel Berlin <dberlin at dberlin.org>
> wrote:
>
>> In particular:
>> "
>> I'm not so sure that it's sufficient. Suppose, for instance, that I
>> wanted to insert a MemoryDef between 1 and 2 in the below
2016 Oct 31
1
[PATCH] D26127: [MemorySSA] Repair AccessList invariants after insertion of new MemoryUseOrDef.
On Sun, Oct 30, 2016 at 5:03 PM, Bryant Wong <
3.14472+reviews.llvm.org at gmail.com> wrote:
> To give this a bit of context, this patch stems from issues that I've
> encountered while porting MemCpyOpt to MSSA.
>
Okay. I'm not sure i would try to port instead of just rewrite. The whole
goal of MemorySSA is to enable us to write memory optimizations in non-N^2
ways.
If
2016 Apr 11
2
[LICM][MemorySSA] Converting LICM pass to use MemorySSA to avoid AliasSet collapse issue
Hi All,
I'm looking into converting LICM to use MemorySSA instead of AliasSets to
determine when it is safe to hoist/sink/promote loads and stores to get
around the issue of alias set collapse (see discussion [1]). I have a
prototype implementation, but have run into two issues that I could use
input from the designers of MemorySSA to resolve:
1) Is MemorySSA intended to be
2017 Apr 28
2
[MemorySSA] A question about how to update the MemorySSA when we call RecursivelyDeleteTriviallyDeadInstructions
...ursively and memory access
instructions may be erased inside the recursive process, we need a way
to update MemorySSA for those instructions. Note MemorySSA update
should be done before the instruction is erased.
Is it acceptable to have an API with MemorySSAUpdater as a param, or
it is better for MemoryUseOrDef to have a callback value handler to do
the update transparently, or there are better ways to be suggested.
Thanks,
Wei.
2016 Apr 20
2
[LICM][MemorySSA] Converting LICM pass to use MemorySSA to avoid AliasSet collapse issue
...a hammer?
@@ -802,17 +836,8 @@ void CachingMemorySSAWalker::invalidateInfo(MemoryAccess *MA) {
doCacheRemove(MA, Q, Q.StartingLoc);
return;
}
- // If it is not a use, the best we can do right now is destroy the cache.
- bool IsCall = false;
-
- if (auto *MUD = dyn_cast<MemoryUseOrDef>(MA)) {
- Instruction *I = MUD->getMemoryInst();
- IsCall = bool(ImmutableCallSite(I));
- }
- if (IsCall)
- CachedUpwardsClobberingCall.clear();
- else
- CachedUpwardsClobberingAccess.clear();
+ CachedUpwardsClobberingCall.clear();
+ CachedUpwardsClobberingAccess.cle...