-
Notifications
You must be signed in to change notification settings - Fork 518
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
NativeAOT: fix warnings in our code #18629
Comments
This was referenced Aug 17, 2023
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Sep 1, 2023
…th NativeAOT. We have numerous methods that we should never end up executing when using NativeAOT, in particular methods called from native code. Ideally we'd be able to link these away completely, but that's a much larger refactoring, so in the meantime we can do something simpler: just throw an exception in these methods if using NativeAOT. There are two advantages: * Smaller apps. * No warnings from NativeAOT about these methods doing things that aren't trimmer-safe. Contributes towards xamarin#18629.
This was referenced Sep 1, 2023
52 tasks
rolfbjarne
added a commit
that referenced
this issue
Sep 5, 2023
…18904) If anything we're supposed to link with *.o files, not publish them, but since we're currently not handling any *.o files, just explicitly remove them from the build. This avoids a warning where ComputeBundleLocation would issue a warning about not knowing what to do with them. Contributes towards #18629. --------- Co-authored-by: Ivan Povazan <55002338+ivanpovazan@users.noreply.github.com>
rolfbjarne
added a commit
that referenced
this issue
Sep 5, 2023
…elegate type. (#18906) This makes it possible to call the generic Marshal.GetDelegateForFunctionPointer<T> method instead of the non-generic Marshal.GetDelegateForFunctionPointer method, which is easier for AOT compilers to handle (no reflection for Marshal.GetDelegateForFunctionPointer<T>). Contributes towards #18629.
rolfbjarne
added a commit
that referenced
this issue
Sep 7, 2023
…th NativeAOT. (#18907) We have numerous methods that we should never end up executing when using NativeAOT, in particular methods called from native code. Ideally we'd be able to link these away completely, but that's a much larger refactoring, so in the meantime we can do something simpler: just throw an exception in these methods if using NativeAOT. There are two advantages: * Smaller apps. * No warnings from NativeAOT about these methods doing things that aren't trimmer-safe. Contributes towards #18629.
Fixed in #18909. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enabling warnings for NativeAOT reports some warnings. We should fix these.
Keeping a list of each of them individually, so they can also be fixed individually.
Ref: #18571.
The text was updated successfully, but these errors were encountered: