search for: scheduel

...pec and writing very minimal code. That turned out to be a good thing, because shortly after that they discovered Ruby. They got all excited about the new possibilities and began building some really (i mean really) cool stuff! Our first deadline came and went and it became more obvious that schedueling a completion date would be difficult. I started to ride them a little harder. Looking for something tangeable. They wern''t asking for money - instead they were doing other jobs. So I forced them to take money, thinking it would make them more committed to my deadlines. All it s...

On May 8, 2012, at 3:02 PM, dag at cray.com wrote: > Hi everyone, > > As I've mentioned before we are doing some work on the LLVM scheduler to > improve it. Specifically, we are working to get loads and stores to > move past each other when possible. > > When I asked about enhancing scheduler heuristics a month or so ago, I > got a response about a MachineInstr

...chineInstr >> scheduler using the trunk implementation as a helpful reference. >> >> If you're developing based on 3.1, don't expect to upstream changes. > > Again, this doesn't answer the questions: > > - What's the expected release time for the new schedueler? 3.2? > > - How difficult do you expect a backport to 3.1 to be? We have to work > from 3.1. Trunk is too buggy. You've stated that trunk is too buggy for you to work from on multiple occasions. Can you elaborate? That doesn't match my experience, as I install a new compile...

...in 3.1, then develop your own MachineInstr > scheduler using the trunk implementation as a helpful reference. > > If you're developing based on 3.1, don't expect to upstream changes. Again, this doesn't answer the questions: - What's the expected release time for the new schedueler? 3.2? - How difficult do you expect a backport to 3.1 to be? We have to work from 3.1. Trunk is too buggy. >> In general, it would be very helpful for folks to post about major >> architectural changes like this before work begins so the rest of us can >> plan our work....

Hi everyone, As I've mentioned before we are doing some work on the LLVM scheduler to improve it. Specifically, we are working to get loads and stores to move past each other when possible. When I asked about enhancing scheduler heuristics a month or so ago, I got a response about a MachineInstr scheduler and that that was the way of the LLVM future. Is that so? Is the ScheduleDAG going

I hired a friend of a friend to build my company a fairly substantial application. He quoted it, committed to it, and now says he has run out of money. I''ve offered him additional money/incentives ...twice. He continues to commit, and then, ultimately not make his commitment. I''m not sure what my options are. Ideally, I would like to simply fire him and hire someone to