Displaying 2 results from an estimated 2 matches for "weak_set".
Did you mean:
seek_set
2014 Sep 10
4
[LLVMdev] Leaks in PBQPBuilderWithCoalescing::build ?
...using some pre-canned memory
> management might help...
>
> Attached is a patch that changes this allocation to use shared_ptr,
> perhaps it'll address the bug?
>
> (ideally we shouldn't need the intrusive ref counting
> (std::enable_shared_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=...
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