search for: regpressuretrack

...15 3 libpthread.so.0 0x00002ad3b4a17340 4 libc.so.6 0x00002ad3b547bcc9 gsignal + 57 5 libc.so.6 0x00002ad3b547f0d8 abort + 328 6 libc.so.6 0x00002ad3b5474b86 7 libc.so.6 0x00002ad3b5474c32 8 clang-3.5 0x0000000001de82a3 9 clang-3.5 0x0000000001de880c llvm::RegPressureTracker::decreaseRegPressure(llvm::ArrayRef<unsigned int>) + 120 10 clang-3.5 0x0000000001dec305 llvm::RegPressureTracker::bumpDownwardPressure(llvm::MachineInstr const*) + 593 11 clang-3.5 0x0000000001dec4da llvm::RegPressureTracker::getMaxDownwardPressureDelta(llvm::MachineInstr const...

...0x00002ad3b547bcc9 gsignal + 57 >> 5 libc.so.6 0x00002ad3b547f0d8 abort + 328 >> 6 libc.so.6 0x00002ad3b5474b86 >> 7 libc.so.6 0x00002ad3b5474c32 >> 8 clang-3.5 0x0000000001de82a3 >> 9 clang-3.5 0x0000000001de880c >> llvm::RegPressureTracker::decreaseRegPressure(llvm::ArrayRef<unsigned >> int>) + 120 >> 10 clang-3.5 0x0000000001dec305 >> llvm::RegPressureTracker::bumpDownwardPressure(llvm::MachineInstr >> const*) + 593 >> 11 clang-3.5 0x0000000001dec4da >> llvm::RegPressureTracker...

...5 libc.so.6 0x00002ad3b547f0d8 abort + 328 > 6 libc.so.6 0x00002ad3b5474b86 > 7 libc.so.6 0x00002ad3b5474c32 > 8 clang-3.5 0x0000000001de82a3 > 9 clang-3.5 0x0000000001de880c > llvm::RegPressureTracker::decreaseRegPressure(llvm::ArrayRef<unsigned > int>) + 120 > 10 clang-3.5 0x0000000001dec305 > llvm::RegPressureTracker::bumpDownwardPressure(llvm::MachineInstr > const*) + 593 > 11 clang-3.5 0x0000000001...

I was handed a makefile which is used to compile a library and was told to figure out why the compilation is failing. There is a lot of output and at this point I'm not sure what is important and what is not. I'm trying to solve this problem in small steps, so if asked I can certainly provide more information. The first error that I see during compilation is

...lgorithm, but if we wang to support more complex scheduling algorithms, for example, modulo scheduling for loops, it seems more easy to accomplish this in SSA form as SSA is more suitable for tracking dependencies and doing code motion. I find that LiveIntervals analysis pass, which is required by RegPressureTracker and MachineScheduler, cannot run before phi elimination. Is this one of the reason that machine scheduling is not done in SSA form? Any explanation is appreciated. Thanks a lot! Cheers, Xing

...but if we wang to support more complex scheduling algorithms, for example, modulo scheduling for loops, it seems more easy to accomplish this in SSA form as SSA is more suitable for tracking dependencies and doing code motion. > > I find that LiveIntervals analysis pass, which is required by RegPressureTracker and MachineScheduler, cannot run before phi elimination. Is this one of the reason that machine scheduling is not done in SSA form? > > Any explanation is appreciated. Thanks a lot! > > > > Cheers, > Xing > > > > ____________________________________________...

...eDAGInstrs::addChainDependency(llvm::SUnit*, llvm::SUnit*, unsigned int) () #2 0x0000000001855519 in llvm::ScheduleDAGInstrs::addChainDependencies(llvm::SUnit*, llvm::ScheduleDAGInstrs::Value2SUsMap&) () #3 0x000000000185f3ba in llvm::ScheduleDAGInstrs::buildSchedGraph(llvm::AAResults*, llvm::RegPressureTracker*, llvm::PressureDiffs*, llvm::LiveIntervals*, bool) () #4 0x00000000017d3c89 in llvm::ScheduleDAGMILive::buildDAGWithRegPressure() () #5 0x00000000017d3d13 in llvm::ScheduleDAGMILive::schedule() () #6 0x00000000017d015e in (anonymous namespace)::MachineSchedulerBase::scheduleRegions(llvm::Sche...