search for: nodemetadata

Hi, I have run into a test case on an out-of-tree target where PBQP fails to complete register allocation after "Attempting to spill already spilled value" (the triggered assert in InlineSpiller::spill(). First, the original LiveInterval is spilled. It is a load of a symbol into a narrow register class, i.e. a subset of the class of address registers. InlineSpiller decides to

...ers, Lang. On 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 c...

> 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...

...dmaison at arm.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> [mai...

...ang 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 c...

> On Aug 3, 2015, at 10:24 AM, Chris Bieneman <beanz at apple.com> wrote: > > Hey Tom, > > I’m not a regular user of llvm-config, but this sounds completely right to me, and it would be a significant improvement over what we have now. > > The only question I want to raise is, what about NDEBUG? There are headers that conditionalize on NDEBUG, which could lead to ABI