search for: isconservativelyallocat

...correct insertion, as the regs did in fact run out in this case. In setup(), the node is first put into not-provably-allocatables. However, one of it's neigbhour invoked handleDisconnectEdge(), and moves it into conservatively-allocatables, because DeniedOpts had become less than NumOpts (in isConservativelyAllocatable(). * There are lots of spillable nodes being popped before the one that can't be spilled. This seems intuitively wrong, as they are intervals that actually could be spilled. I would really appreciate some help and pointers on what might be going wrong here, Jonas Paulsson --------------...

...n Mon, Jan 26, 2015 at 11:42 PM, Arnaud A. de Grandmaison < arnaud.degrandmaison at arm.com> wrote: > > A node should never be put into the conservatively allocatable list if > there is a chance of it spilling. > > > > I can understand why the logic of > NodeMetadata::isConservativelyAllocatable is necessary for the node to be > allocatable, but I have not been able to convince myself this is > sufficient, especially when the node degree > available registers. > > > > Cheers, > > Arnaud > > > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmde...

> A node should never be put into the conservatively allocatable list if there is a chance of it spilling. I can understand why the logic of NodeMetadata::isConservativelyAllocatable is necessary for the node to be allocatable, but I have not been able to convince myself this is sufficient, especially when the node degree > available registers. Cheers, Arnaud From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Lang Hames Sen...

....com] Sent: den 27 januari 2015 08:43 To: 'Lang Hames'; Jonas Paulsson Cc: llvmdev at cs.uiuc.edu Subject: RE: [LLVMdev] PBQP crash > A node should never be put into the conservatively allocatable list if there is a chance of it spilling. I can understand why the logic of NodeMetadata::isConservativelyAllocatable is necessary for the node to be allocatable, but I have not been able to convince myself this is sufficient, especially when the node degree > available registers. Cheers, Arnaud From: llvmdev-bounces at cs.uiuc.edu<mailto:llvmdev-bounces at cs.uiuc.edu> [mailto:llvmdev-bounces at cs...

...; Jonas Paulsson > *Cc:* llvmdev at cs.uiuc.edu > *Subject:* RE: [LLVMdev] PBQP crash > > > > > A node should never be put into the conservatively allocatable list if > there is a chance of it spilling. > > > > I can understand why the logic of > NodeMetadata::isConservativelyAllocatable is necessary for the node to be > allocatable, but I have not been able to convince myself this is > sufficient, especially when the node degree > available registers. > > > > Cheers, > > Arnaud > > > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmde...