Displaying 4 results from an estimated 4 matches for "dst_block".
Did you mean:
dst_blocks
2002 Apr 16
2
Can rsync update files in place?
I've just subscribed, but a search of the archive doesn't indicate this
has been handled before...
Is there a way to get rsync to not create a new file while transferring
and then rename it, but to instead update the existing file in place,
i.e. simply write those blocks that have been updated and leave the rest
alone?
That would be ideal for what I wanted rsync for, namely updating
2006 Jul 05
0
[LLVMdev] Critical edges
...ddPreserved<DominanceFrontier>();
AU.addPreserved<LoopInfo>();
AU.addPreservedID(LoopSimplifyID);
}
bool CriticalEdgeRemoval_Fer::runOnMachineFunction
(MachineFunction & mf) {
std::vector<MachineBasicBlock *> src_blocks;
std::vector<MachineBasicBlock *> dst_blocks;
// first, only find the critical edges:
for(unsigned u = 0; u < mf.size(); u++) {
MachineBasicBlock * mbb = mf.getBlockNumbered(u);
for(MachineBasicBlock::succ_iterator succ = mbb->succ_begin();
succ != mbb->succ_end(); succ+...
2006 Jul 04
2
[LLVMdev] Critical edges
On Tue, 4 Jul 2006, Fernando Magno Quintao Pereira wrote:
> However, it does not remove all the critical edges. I am getting a very
> weird dataflow graph (even without the Break Critical edges pass). The
> dataflow generated by MachineFunction::dump() for the program below is
> given here:
> http://compilers.cs.ucla.edu/fernando/projects/soc/images/loop_no_crit2.pdf
...
> The
2007 Aug 19
1
[LLVMdev] MBB Critical edges
...e machine function control
// flow graph.
//===---------------------------------------------------------------------===//
bool CriticalEdgeRemoval_Fer::runOnMachineFunction(MachineFunction & mf) {
std::vector<MachineBasicBlock *> src_blocks;
std::vector<MachineBasicBlock *> dst_blocks;
for(unsigned u = 0; u < mf.size(); u++) {
MachineBasicBlock * mbb = mf.getBlockNumbered(u);
for(MachineBasicBlock::succ_iterator succ = mbb->succ_begin();
succ != mbb->succ_end(); succ++) {
MachineBasicBlock *...