Displaying 2 results from an estimated 2 matches for "tmp1542_i".
Did you mean:
tmp1505_i
2008 May 22
1
[LLVMdev] Eliminate Store-Load pair even the LoadInst is volatile
...m and got the following .ll code:
...
%r1419_0_0_0_i376 = alloca i32 ; <i32*> [#uses=2]
...
%tmp1476_i = lshr i32 %tmp1226_i, 24 ; <i32> [#uses=1]
store i32 %tmp1476_i, i32* %r1419_0_0_0_i376, align 4
%tmp1505_i = volatile load i32* %r1419_0_0_0_i376, align 4 ; <i32> [#uses=1]
%tmp1542_i = getelementptr [256 x i8]* @Te, i32 0, i32 %tmp1505_i
...
llvm opt can't remove the redundant store-load pair to just use the value
%tmp1476 as the load is volatile.
But I think for the above situation, it's safe to remove store-load, as the
allocad %r1419_0_0_0_i376 just has two users...
2008 May 23
1
[LLVMdev] Eliminate Store-Load pair even the LoadInst is volatile
...lt;i32*> [#uses=2]
> > ...
> > %tmp1476_i = lshr i32 %tmp1226_i, 24 ; <i32> [#uses=1]
> >
> > store i32 %tmp1476_i, i32* %r1419_0_0_0_i376, align 4
> > %tmp1505_i = volatile load i32* %r1419_0_0_0_i376, align 4 ; <i32>
> [#uses=1]
> >
> > %tmp1542_i = getelementptr [256 x i8]* @Te, i32 0, i32 %tmp1505_i
> > ...
> >
> >
> > llvm opt can't remove the redundant store-load pair to just use the value
> %tmp1476 as the load is volatile.
> > But I think for the above situation, it's safe to remove store-load,...