Introduce concept of blocking extern functions for better interop of GC with foreign code
#3116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed as blocking have a special handling in the GC - upon transiting from managed to unmanaged execution (Scala to Native library) informatin about current stacktop and content of registers is saved. It it used to skip waiting for potentially blocking thread in the StopTheWorld event
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce the concept of blocking extern functions.
Extern functions marked as blocking have special handling in the GC - upon transiting from managed to unmanaged execution (Scala to Native library) information about the current stack top and content of registers is saved to allow for GC.
It is used to skip waiting for potentially blocking threads in the StopTheWorld event, in case the given thread is executing a blocking syscall, eg. waiting for socket connect or reading from a file.
This change allows us to shorten the time spent when synchronizing the threads in case of StopTheWorld event, and does not require us to interrupt threads in order to force they're execution to reach safepoint.
scala.scalanative.unsafe.blockingannotationisBlockingattribute to NIR as field ofAttr.Extern@blockingannotation in the compiler plugin