Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
MonoTouch 6.0.8 release notes say:
Runtime Trampolines: It is no longer necessary to manually manage trampolines in the Mono runtime, trampolines are now handled dynamically.
What does this mean? How do you manually manage trampolines anyway?
Do you still need to add compiler flags when you know you’re probably going to run out of trampolines?
This means just as the release notes say that Monotouch now figures out how many trampolines to allocate.
To add more trampolines you add compiler flags such as:
Usually when you were running out of trampolines meant that you were using a lot of generics and interfaces, which are hard to calculate how much memory needs to be allocated for ahead of time (aot). So Xamarin must have found a magic way to do this calculation and allocate the trampolines accordingly. I couldn’t find more information about this.
There’s a bit more information about trampolines in general in this thread: http://forums.xamarin.com/discussion/503/trampolines-cost and this thread which was prior to the other one: http://lists.ximian.com/pipermail/monotouch/2012-March/008800.html