search for: _moves_

...ocations over WAN). Overall it works flawlessly, as it transfers only changes, but sometimes there are some serious hiccups. Suppose this scenario, suppose it's 1 GB of files: user shares: /home/joe/data/file1 /file2 /... /file1000 Now the user _moves_ that data to some other folder: /home/joe/WAN_goes_crazy/file1 /file2 /... /file1000 ...and we start a backup process. rsync will first transfer data from "/home/joe/WAN_goes_crazy/file...", and then dele...

...br loopstart loopbody: [use alloc'd mem] call stackrestore(%oldsp) br loopstart loopstart: %oldsp = call stacksave() alloca [...] brcond loopbody, end end: [use alloc'd mem] call stackrestore(%oldsp) Then LoopRotation clones the stacksave from bb3 to bb1 and _moves_ the alloca from bb3 to bb1. So the alloca is moved outside the loop instead of having it execute each lap. But there still is a stackrestore inside the loop that will "deallocate" the memory, so all but the first lap of the loop will access deallocated memory. So, shouldn't alloca in...

...ll stackrestore(%oldsp) >   br loopstart > > loopstart: >    %oldsp = call stacksave() >   alloca >   [...] >   brcond loopbody, end > > end: >   [use alloc'd mem] >   call stackrestore(%oldsp) > > Then LoopRotation clones the stacksave from bb3 to bb1 and _moves_ the > alloca from bb3 to bb1. So the alloca is moved outside the loop instead > of having it execute each lap. But there still is a stackrestore inside > the loop that will "deallocate" the memory, so all but the first lap of > the loop will access deallocated memory. > &gt...

Hi, I have two problems regarding the llvm.stackrestore intrinsic. I'm running on 3.0, but a quick test on trunk also showed the same behavior. First problem: --------------- I have code like: tmp1 = call llvm.stacksave() tmp2 = alloca [do some stuff with tmp2] call llvm.stackrestore(tmp1) [some other stuff] tmp3 = call llvm.stacksave() tmp4 = alloca [do some stuff