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

Allocation stubs should account for PageSpace::IsPageAllocatableSize #3984

Closed
iposva-google opened this issue Jul 4, 2012 · 6 comments
Closed
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@iposva-google
Copy link
Contributor

Currently we end up allocating objects that should reside in large pages in the new space. Evaluate whether we want to allocate as many objects as we can in new space or whether we should honor the large object boundary.

@iposva-google
Copy link
Contributor Author

Set owner to @mraleph.

@mraleph
Copy link
Member

mraleph commented Sep 7, 2012

Moving to Milestone-Later because it does not seem to be causing any problems.


Removed the owner.
Added this to the Later milestone.

@iposva-google
Copy link
Contributor Author

Removed Priority-Medium label.
Added Priority-Unassigned label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@iposva-google iposva-google added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Aug 4, 2014
@iposva-google
Copy link
Contributor Author

Stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

4 participants