Displaying 2 results from an estimated 2 matches for "createloadsandstoreupdat".
Did you mean:
createloadsandstoreupdater
2017 Feb 17
2
[MemorySSA] inserting or removing memory instructions
Hi guys,
a question about updating memory SSA:
Is it expected that e.g insertion of MemoryDef doesn't change all dominated
uses?
For example test case CreateLoadsAndStoreUpdater produces:
define void @F(i8*) {
; 1 = MemoryDef(liveOnEntry)
store i8 16, i8* %0
; 4 = MemoryDef(1)
store i8 16, i8* %0
br i1 true, label %2, label %3
; <label>:2: ; preds = %1
; 2 = MemoryDef(4)
store i8 16, i8* %0
br label %4
; <label&g...
2017 Feb 17
2
[MemorySSA] inserting or removing memory instructions
...sinking
> them, not actually changing the aliasing.
> The test does not obviously test this constraint, and is pretty contrived.
> If you have a use case where we need to rename affected uses, i'm happy to
> make it do that, it's trivial.
>
>
>> For example test case CreateLoadsAndStoreUpdater produces:
>>
>> define void @F(i8*) {
>> ; 1 = MemoryDef(liveOnEntry)
>> store i8 16, i8* %0
>> ; 4 = MemoryDef(1)
>> store i8 16, i8* %0
>> br i1 true, label %2, label %3
>>
>> ; <label>:2: ; p...