Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Memory allocation strategy #233

Closed
AndyAyersMS opened this issue Mar 3, 2015 · 2 comments
Closed

Memory allocation strategy #233

AndyAyersMS opened this issue Mar 3, 2015 · 2 comments
Assignees
Milestone

Comments

@AndyAyersMS
Copy link
Member

The JIT can't leak memory, and ideally all allocation it does is into some controlled pool. We need to figure out how to modify LLVM's allocation and our own so that this happens.

Russ owns this for now.

See also #225.

@russellhadley
Copy link
Contributor

Move this out.

@russellhadley
Copy link
Contributor

There's no easy way to use a particular pool. I'm shifting gears to look into better analysis tools to track leaks. Moving to 84.

@russellhadley russellhadley modified the milestones: Sprint 84, Sprint 83 Jun 3, 2015
@russellhadley russellhadley modified the milestones: Sprint 85, Sprint 84 Jun 18, 2015
@russellhadley russellhadley modified the milestones: Sprint 86, Sprint 85 Jul 2, 2015
@russellhadley russellhadley modified the milestones: Sprint 87, Sprint 86 Jul 23, 2015
@russellhadley russellhadley modified the milestones: Sprint 88, Sprint 87 Aug 14, 2015
@russellhadley russellhadley modified the milestones: Sprint 90, Sprint 88 Sep 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants