[CoreCLR] Support marshal methods #9901
Closed
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.
This is a follow-up to #9805 and #9900
The goal of this PR is to enable marshal methods in CoreCLR. This involves these changes:
xamarin_app_initmethod is added to the pinvoke overridesmanagedMarshalMethodsLookupEnabledis set before callingJNIEnvInit.Initializein the CoreCLRhost.cc_mm_wrappermethod for methods which already have[UnmanagedCallersOnly]attributes inMarshalMethodsAssemblyRewriter. There was a bug in [Experimental] Add alternative way of resolving UCO function pointers for Marshal Methods #9805 which created an_Activate_mm_mm_wrapperUCO which called the hand-writtenn_Activate_mmUCO. This wasn't caught earlier because Mono does not throw when a managed function calls an UCO. On CoreCLR, this codepath failed withInvalid Program: attempted to call a UnmanagedCallersOnly method from managed code..