Displaying 2 results from an estimated 2 matches for "0b0jpkch3ic_7txfvu2hccupfzxm".
2014 Sep 10
4
[LLVMdev] Leaks in PBQPBuilderWithCoalescing::build ?
...from_this) but instead have a weak_set that has
> std::weak_ptr in it & implicitly removes elements as they become null
> (probably on a harvesting schedule, rather than with a direct callback as
> is currently implemented))
> pbqp_leak.diff
> <https://docs.google.com/file/d/0B0jpkch3iC_7TXFVU2hCcUpfZXM/edit?usp=drive_web>
>
>
> On Wed, Sep 10, 2014 at 3:19 PM, Arnaud A. de Grandmaison <
> arnaud.degrandmaison at arm.com> wrote:
>
>> Hi Lang,
>>
>>
>>
>> In PBQPBuilderWithCoalescing::build, around line 360, we have code
>> looking like:...
2014 Sep 10
4
[LLVMdev] Leaks in PBQPBuilderWithCoalescing::build ?
Hi Lang,
In PBQPBuilderWithCoalescing::build, around line 360, we have code looking like:
…
PBQP::Vector newCosts(g.getNodeCosts(node));
addPhysRegCoalesce(newCosts, pregOpt, cBenefit);
g.setNodeCosts(node, newCosts);
…
I suspect the leak occurs around the setNodeCosts method, and I have trouble understanding how it handles the case where the node already has costs.
It seems to