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

[JIT] Use reference counting for maintaining multiple code copies #944

Merged
merged 1 commit into from Aug 20, 2018

Conversation

bdw
Copy link
Contributor

@bdw bdw commented Aug 19, 2018

We take some care to make executable memory read/executable, so they are
mmap()'d. The copied' frames would have malloc()'d memory. It is
probably better to treat them as shared resources and use reference
counting to decide when to actually destroy them.

This may be the fix to some bugs, and it may not (JIT code copy and destruction both ought to be rare).

We take some care to make executable memory read/executable, so they are
mmap()'d. The copied' frames would have malloc()'d memory. It is
probably better to treat them as shared resources and use reference
counting to decide when to actually destroy them.
@bdw bdw self-assigned this Aug 19, 2018
@bdw bdw requested review from jnthn and niner August 19, 2018 20:37
@jnthn
Copy link
Member

jnthn commented Aug 19, 2018

Looks sane to me, though @niner can probably do a better review, having been in that bit of the code recently.

@niner niner merged commit 02de10c into master Aug 20, 2018
@coke coke deleted the jitcode-refcount branch February 9, 2022 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants