There are no functional changes here, just code simplification.

…are warnings.

…iguration.Report method.

Since LinkerConfiguration.Report uses the trimmer's API to report warnings and errors.

…turn exceptions.

Without having to throw them.

…monotouch-test.

…r on.

There are no functional changes here, just refactoring to make code easier to re-use.

…r on.

There are no functional changes here, just refactoring to make code easier to re-use.

…r on.

There are no functional changes here, just refactoring to make code easier to re-use.

This new mode is still considered a 'Static' registrar mode, it's just a variation of it.

This way we can ask the linker to inline the Runtime.IsManagedStaticRegistrar property, and remove any dead code paths.

…ManagedRegistrarLookupTablesStep.

…current registrar mode is 'ManagedStatic'.

…egistrar

The managed static registrar will add code to the processed assemblies, which means
it must run before the trimmer sweeps unused code.

This means we have to split the current registrar logic in two:

1. First we process all the assemblies.
2. Then we write out the results.

When not using the managed static registrar, these two steps happens right after
oneanother (like they do now), while when using the managed static registrar, the
processing is done before the trimmer sweeps (where we'll also generate all the new
IL code), and then the generated native code will be done at the end of the build
process (like for the old-school static registrar).

…ed static registrar step can access them.

There are no functional changes here, just refactoring to make code easier to re-use.

Comparing -1 to 0xFFFFFFFF doesn't get the right result otherwise.

…ve-C method signatures.

This is required when generating a cast of a function pointer to an Objective-C method
signature (which the managed static registrar does).

It's not needed until later anyway.

This way we can add code for the managed static registrar (which does not need the
token reference, in fact creating a token reference for a method won't be possible
with the managed static registra) in the correct location in the code.

This makes it easier to use this code from the managed static registrar.

… attribute (if any)

…ith Cecil.

…ypes when emitting IL code with Cecil.

…ssor to make it easier to reuse.

…enerating native code when using the managed static registrar.

When using the managed static registrar, we register types with the static registrar
before the linker does its work, so we need to follow-up after the linker has figured
out what will be trimmed away to remove any such types from the list of registered types.

…r on.

This is to make the Class.ResolveToken usable from the managed static registrar.

…llersOnly] method.

Add an API to look up the native symbol for an [UnmanagedCallersOnly] method from native code.

This adds a managed static registrar, which is a variation of the static registrar
that takes advantage of a few new features in C# and the runtime, as well as avoiding
metadata tokens, which NativeAOT doesn't support.

This registrar will generate most of the trampoline/interop code as managed code
using Cecil, and the Objective-C part is as small as possible.

Fixes xamarin#17324.

…gedCallersOnly method from the managed static registrar

…for later reference by the static registrar

…messages.

This commit introduces a few new GetNSObject/GetINativeObject overloads that will
be used by the managed static registrar.

…ceIdentification in exported methods.

MidiCIDeviceIdentification isn't blittable ((yet)[1]), so exporting it makes
the AOT compiler complain. Use a different (but blittable) type instead in the
test.

[1]: xamarin@03f0a35

…sing the managed static registrar.

…ral.CreateBlockForDelegate.

Co-authored-by: Haritha Mohan <harithamohan@microsoft.com>

Co-authored-by: Haritha Mohan <harithamohan@microsoft.com>

…edCallersOnly method with an underscore in .NET 8+.

Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Co-authored-by: Ivan Povazan <55002338+ivanpovazan@users.noreply.github.com>

Co-authored-by: Ivan Povazan <55002338+ivanpovazan@users.noreply.github.com>

Otherwise the linker will remove them.

Co-authored-by: Filip Navara <filip.navara@gmail.com>

Add a few more helper methods to get method references, that simplifies calling code.

…ment in UnmanagedCallersOnly methods in the managed static registrar.

This fixes invalid IL in a few cases.

…arameter.

It's only called from one place, and the flags are constant, so just hardcode
the value in the method instead of taking it as an input. This simplifies the
generated managed static registrar code a little bit.

…in generated method bodies.

…icable code paths.

…ime.GetNSObject

We can't call the generic Runtime.GetNSObject<T> method when we don't know the final
type of the returned object, which happens for open types. However, we must always
call the generic Runtime.GetNSObject<T> when we know the final type, so that we have
the correct object type on the evaluation stack.

Fix this by properly detecting open types and only calling Runtime.GetNSObject in
that case.

…voke.

Keep better track of whether we're calling MethodBase.Invoke to call the target method,
which allows us to detect certain error scenarios (and show a corresponding error).

… 'object' reference is left on the stack.

Keep track of when we called MethodBase.Invoke and an 'object' reference is left
on the stack, so that we can cast to the appropiate type later on when we know how
the value is converted to the corresponding native type.

This fixes a few cases of the managed static registrar creating unverifiable IL.

…able

…ypes.

We can't create an instance of a generic type in the UnmanagedCallersOnly trampoline,
so simplify the code to not even try, and instead just throw the final exception.