search for: femtopairablepass

...ked the node cost for this register, which is correctly set to inf for spill, as well as the edge costs, and they look ok. I also attached my target's pbqp related file in case you want to double check what I did. This is llvm-3.0 based. It comprises 2 passes : the FemtoPBQPBuilder, plus a FemtoPairablepass, which undo some of the coalescer's work. The insertRegCopy may specifically need a double check, as I am not 100% sure to have updated correctly the LiveInterval information. In terms of registers, the Femto target is simplistic : a single register class GR16, for data and pointers, all i1...

...s register, which > is correctly set to inf for spill, as well as the edge costs, and they look > ok. > > I also attached my target's pbqp related file in case you want to double check > what I did. This is llvm-3.0 based. It comprises 2 passes : the > FemtoPBQPBuilder, plus a FemtoPairablepass, which undo some of the coalescer's > work. The insertRegCopy may specifically need a double check, as I am not 100% > sure to have updated correctly the LiveInterval information. > > In terms of registers, the Femto target is simplistic : a single register > class GR16, for data...

...correctly set to inf for spill, as well as the > > edge costs, and they look ok. > > > > I also attached my target's pbqp related file in case you want to double > > check what I did. This is llvm-3.0 based. It comprises 2 passes : the > > FemtoPBQPBuilder, plus a FemtoPairablepass, which undo some of the > > coalescer's work. The insertRegCopy may specifically need a double > > check, as I am not 100% sure to have updated correctly the LiveInterval > > information. > > > > In terms of registers, the Femto target is simplistic : a single &gt...

...as > > > the > > > edge costs, and they look ok. > > > > > > I also attached my target's pbqp related file in case you want to > > > double check what I did. This is llvm-3.0 based. It comprises 2 > > > passes : the FemtoPBQPBuilder, plus a FemtoPairablepass, which undo > > > some of the coalescer's work. The insertRegCopy may specifically > > > need a double check, as I am not 100% sure to have updated > > > correctly the LiveInterval information. > > > > > > In terms of registers, the Femto target is...

...l, as well as the > > > edge costs, and they look ok. > > > > > > I also attached my target's pbqp related file in case you want to > double > > > check what I did. This is llvm-3.0 based. It comprises 2 passes : the > > > FemtoPBQPBuilder, plus a FemtoPairablepass, which undo some of the > > > coalescer's work. The insertRegCopy may specifically need a double > > > check, as I am not 100% sure to have updated correctly the LiveInterval > > > information. > > > > > > In terms of registers, the Femto target is s...

...>> the >>>> edge costs, and they look ok. >>>> >>>> I also attached my target's pbqp related file in case you want to >>>> double check what I did. This is llvm-3.0 based. It comprises 2 >>>> passes : the FemtoPBQPBuilder, plus a FemtoPairablepass, which undo >>>> some of the coalescer's work. The insertRegCopy may specifically >>>> need a double check, as I am not 100% sure to have updated >>>> correctly the LiveInterval information. >>>> >>>> In terms of registers, the Femto t...

Hi Arnaud, LiveInterval::markNotSpillable() sets the live interval's spill weight to infinity. For well-formed PBQP graphs (i.e. ones that have some finite-cost solution), PBQP should never chose to spill such an interval. The two possibilities for this crash are that the input graph has no finite-cost solution, or that you've exposed a bug in the PBQP solver. >From memory your target

...;>> edge costs, and they look ok. > >>>> > >>>> I also attached my target's pbqp related file in case you want to > >>>> double check what I did. This is llvm-3.0 based. It comprises 2 > >>>> passes : the FemtoPBQPBuilder, plus a FemtoPairablepass, which undo > >>>> some of the coalescer's work. The insertRegCopy may specifically > >>>> need a double check, as I am not 100% sure to have updated > >>>> correctly the LiveInterval information. > >>>> > >>>> In terms...

Hi All, I finally had a chance to get back to my pbqp trials, now using the 3.0 release. I still hit the same assert : "Attempting to spill already spilled value." This is triggered because in RegAllocPBQP::mapPBQPToRegAlloc, a vreg node is either : - a physical register (problem.isPRegOption(vreg, alloc)), - or a spill (problem.isSpillOption(vreg, alloc)) The problem is that pass