Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arena allocations #38

Open
mverleg opened this issue Mar 25, 2018 · 1 comment
Open

Arena allocations #38

mverleg opened this issue Mar 25, 2018 · 1 comment

Comments

@mverleg
Copy link
Collaborator

mverleg commented Mar 25, 2018

There are three things to consider:

  1. The total required size of an arena should be known beforehand.
  2. All the data in an arena should be cleaned up at the same time.
  3. It may impact multithreading (either not sync, or too many atomic operations).

For #1, while its impossible to know the amount of memory required, it is acceptable to use multiple arena's.
For #2, this should be easy, as most things are needed until the end of compilation.
For #3, this remains an open issue, but can be delayed until multi-threading is actually added.

@mverleg
Copy link
Collaborator Author

mverleg commented Apr 10, 2018

This could be combined with flyweight, maybe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant