search for: vregstoalloc

...se is compiling. J > > The last issue I have is an assert during regalloc in LiveIntervalAnalysis > : “attempt to spill already spilled interval!”, and I do not know where to > start looking. Any hint would be welcome. > > The data structure you want to keep your eye on is the set vregsToAlloc to RegAllocPBQP. This set holds the virtual registers which PBQP must allocate for on its next round. Once a virtual register has been spilled it should be erased from this set (see RegAllocPBQP::mapPBQPToRegAlloc), and it should never re-enter it, and thus never be considered again by the PBQP all...

...the contraints right. I was surprised to have to add a "safety net" to prevent the impossible case; at first I though pbqp could "backtrack" once it discovers it gets to an impossible case... My backend is private, so I can not share it. I will trace what's happening with vregsToAlloc and keep you updated. Regards, -- Arnaud de Grandmaison ________________________________ From: Lang Hames [mailto:lhames at gmail.com] Sent: Friday, June 17, 2011 9:37 AM To: Arnaud Allard de Grandmaison Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] PBQP & register pairing Hi Arnaud, Th...

Attached is a small patch to allow users of the PBQP allocator to optionally insert a custom pass. I believe it can be usefull to other users of the pbqp. I used it to undo some of the coalescer work, and make sure that I have different virtual registers, inserting a copy if necessary, to build a pair. I noticed an unexpected --- to me at least --- behaviour of the allocator. I have some