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.

Sign up for GitHub

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

Jump to bottom

[2018-08][watchos] Use mono_dangerous_add_raw_internal_call for watchOS icalls #5030

Merged
merged 2 commits into from
Oct 26, 2018
Merged

[2018-08][watchos] Use mono_dangerous_add_raw_internal_call for watchOS icalls #5030

merged 2 commits into from
Oct 26, 2018

Commits on Oct 25, 2018

  1. Add optional mono_dangerous_add_raw_internal_call to exports.t4

    @lambdageek
    lambdageek committed Oct 25, 2018
    Configuration menu
    Copy the full SHA
    ecaa3ac View commit details
    Browse the repository at this point in the history

  2. Use mono_dangerous_add_raw_internal_call on watchOS for icall registr… 

    …ation

Internal calls added with mono_dangerous_add_raw_internal_call run in GC Unsafe
mode under cooperative and hybrid suspend, whereas internal calls added with
mono_add_internal_call run in GC Safe mode since
mono/mono@5756ba4 in order for hybrid suspend
to be a transparent replacement for preemptive suspend (the old default).  The
icalls in GC Unsafe mode have a responsibility not to block indefinitely
without manually performing a thread state transition to GC Safe mode, and in
return they avoid a thread state transition when the icall is invoked from a
managed method.
    @lambdageek
    lambdageek committed Oct 25, 2018
    Configuration menu
    Copy the full SHA
    cc2f1a4 View commit details
    Browse the repository at this point in the history